Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
csirac2
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
61.
▲
by
csirac2
11y ago
I think they're not rated as anything. They simply have no manufacturer-supplied licensing/approvals whatsoever. So it is up to the user to gain an appropriate license and operate them to the conditions stipulated by that license.
62.
▲
by
csirac2
11y ago
Do you have any FCC certified SDR kit currently? This only impacts an OEM/importer's ability to gain FCC approval/certification for new devices. If you're not slapping FCC stickers on things, or are using something that
63.
▲
by
csirac2
11y ago
They are struggling with a very simple problem. If you configure your 5GHz U-NII device to the wrong country, and turn it on, it will stomp all over licensed/restricted spectrum. That's because unlike 2.4GHz, 5GHz has been carved
64.
▲
by
csirac2
11y ago
Which, in practice, means any computer/electronic device that has a radio in it. No. FCC approvals apply to the modular transmitter. Another approval may apply to the overall device.
65.
▲
by
csirac2
11y ago
NICTA/UNSW have apparently started working on a QubesOS port https://my.cse.unsw.edu.au/thesis/thesis_topic_details.php?I... http://sel4.systems/pipermail/devel/2015-March/000312.htm
66.
▲
by
csirac2
11y ago
I agree, and I do (if I end up actually keeping a piece of software running). It's also quite likely that a pre-built docker image isn't going to satisfy everyone's deployment requirements. Starting out with a philosophy that
67.
▲
by
csirac2
11y ago
> But I still think that using docker is probably better than having the user do that manually When it comes to deploying, supporting and securing complex web application software, it is very rare that an out-of-the-box reference image f
68.
▲
by
csirac2
11y ago
> But in reality of course it's not laziness, it's efficiency. They can get on with other tasks sooner than before. Indeed, and I use Docker myself to improve my own efficiency, and I've seen great stuff built with Docker
69.
▲
by
csirac2
11y ago
Well yes, the fact they chose to require that the webapp have a superuser database account is not docker-specific, but the manner (and it should be said: ease) with which docker is used to neatly package an opaque ball of string creates a t
70.
▲
by
csirac2
11y ago
If you're lucky enough to run in a production environment that has zero configuration policy or minimum security requirements, then yes, granting your webapp superuser privs to the database mightn't be a deal-breaker. For everyo
71.
▲
by
csirac2
11y ago
I love Docker; it's solved a lot of problems for me. But this article highlights the laziness that it can enable: there has to be a middle ground between traditional package management and all of the curation/QA that goes into get
72.
▲
by
csirac2
11y ago
I've tried to install the exact software the author of this article was trying to install, and he/she/they didn't even encounter the insanity that turned me off. There's giving up on traditional package management
73.
▲
by
csirac2
11y ago
As a happy Docker user with a lot of respect for what Docker has achieved, what concerns me is that Docker is clearly an enabler for people to totally abandon proper release and dependency management along with sane sysadmin friendly config
74.
▲
by
csirac2
11y ago
Luckily some disciplines have a journal of negative results :-) Eg. http://www.jnr-eeb.org/index.php/jnr
75.
▲
by
csirac2
11y ago
This is a pretty old article, and well before this time markov/bayesian stuff was already in full swing for bioinformatics, AFAIK. Biology draws from many disciplines, and it's taken a lot of computer science to get to where it is
76.
▲
by
csirac2
11y ago
I suspect you'd run unikernels under Geode. Instead of targeting Xen resources and Xen event/message channels and Xen security modules/FLASK, MirageOS would target Geode instead but perhaps have slightly higher-level resource
77.
▲
by
csirac2
11y ago
I can appreciate that it's been a bit like that, but isn't the truth really somewhere in between? Oversized egos are a problem at the best of times in open source, especially in the kernel. Which has traditionally had a culture of
78.
▲
by
csirac2
11y ago
My contract says my title is software engineer, but titles don't mean much in a small company. Which I kind of like. That said, I didn't study Software Engineering at university. And so, in almost 10 years in various roles writing
79.
▲
by
csirac2
11y ago
URLs are a big deal, and I absolutely loathe systems which actively sabotage likability on the web. That said, it really was an offline app. We could've done it as a native Qt or .NET app. Even so, the standard AngularJS document fragm
80.
▲
by
csirac2
11y ago
We used the Angular document fragment URLs, so it was possible to copy-paste and bookmark things.
81.
▲
by
csirac2
11y ago
Around 2012 I worked with a team migrating some content from a very large static HTML site dating back to 1992. We scoffed at the awful ad-hoc nature of it all, just a pile of static hand-coded HTML pages. But the 2002-2005 stuff had aged m
82.
▲
by
csirac2
11y ago
I've only been exposed to this in oil & gas, but there is a problem that non-destructive testing of drill stems does not test for all failure modes Edit: i.e. NDT'd pieces are not immune from failure (but other factors such as
83.
▲
by
csirac2
11y ago
I was working with someone who thought I was stupid for insisting on integer or fixed-point maths for what I insisted would be a particularly troublesome piece of functionality. They were more experienced, convinced me I was being pedanti
84.
▲
by
csirac2
11y ago
Yeah, I totally get it - I realized I'm a hypocrite when I posted this; just a few weeks ago I put a custom build environment together with an obscure version of gcc because I'm dealing with some code that depends on some of those
85.
▲
by
csirac2
11y ago
I'm a huge fan of docker, but I've also drawn a comparison to linking in the past: some people are using it to defer (not solve!) Dependency management and distro ecosystem complexities. Fossilizing dependencies is not the future;
86.
▲
by
csirac2
11y ago
I spent a week pulling apart our old build scripts (which were dysfunctional) and putting it all back together again with something new. I'd have done almost the same amount of work if I had stuck with make. In fact I spent two days do
87.
▲
by
csirac2
11y ago
I recently spent a week replacing all Makefiles in a reasonably complex embedded arm project I maintain with apenwarr's redo [1] (revamping our cobbled-together CI).. Which allows recursive make structured .do files, without tbe downsi
88.
▲
by
csirac2
11y ago
That's awesome. Would love to know more. I was (only tangentially, really it was my manager) involved with (one of many) LIMS evaluations at CSIRO. I'm under the impression that "Generic" LIMS have awful track records in
89.
▲
by
csirac2
11y ago
As a heavy btrfs user backups have always been on my mind. I run a lab with a handful of busy VMs, all using btrfs. I was frustrated that there were no backup solutions (at the time) which leveraged btrfs, so I created snazzer [1] (one day
90.
▲
by
csirac2
11y ago
To be fair I just trawled through that thread and found your posts most obsessive, and Zed seemingly sticking to technical discussion with (for him) not all that much profanity. Now, not that I disagree with your assertions (epoll/poll
More ›