EU being EU, I can only imagine there's a bunch of particular rules around research that may or may not work in the authors' favor.
87 karma · joined March 17, 2014
EU being EU, I can only imagine there's a bunch of particular rules around research that may or may not work in the authors' favor.
Kulturministeriet (The Danish agency for Culture and Palaces) has a great section on the Cold War ("Kold Krig" in Danish) at https://slks.dk/omraader/kulturarv/bevaringsvaerdige-bygning.... (Google Translate: https://slks-dk.translate.goog/omraader/kulturarv/bevaringsv...).
There'a also a book, Kold Krig, which is available as a PDF at https://slks.dk/fileadmin/publikationer/Kulturarv/Kold_Krig_... (but I can't make Google translate ... translate)
And I still have to visit www.reganvest.dk some day :)
Assuming a memory error somewhere:
On ZFS you'd be writing bad data with a bad checksum, which would be caught by ZFS later on.
On (most) other filesystems you'd be writing bad data and no checksum, and you'd be none the wiser until garbage comes back.
It's a myth that ZFS requires ECC memory; ZFS is safer when running with ECC, but without ECC it will still save your data in a lot of places where most other filesystems won't.
See https://www.reddit.com/r/zfs/comments/7ng231/does_a_zfs_mirr... for a bunch of links on this.
https://news.ycombinator.com/item?id=13643025 https://news.ycombinator.com/item?id=18235798
(I ended up setting different terminal prompts depending on which domain the current machine was under.)
No more jet-lagged minors twice a year, no more train tickets stamped ~200 years in the future (yes, that has happened to me) and no more confusing server logs with odd duplicates.
Also, contact your local EU parliament member and politely explain why this is good...
By default all GPS units have some built-in limits (so-called COCOM
limits) that prevents them from providing any data if the velocity
exceeds 515 m/s at altitudes above 18 km. These artificial limits are
built into GPS receivers to prevent bad guys from using them in
missiles and other nasty stuff.
... and proceed to figure out a way around ...It actually turned out that the change caused the EV sales all but stop completely (quite to the surprise of the tax authorities). So they're looking at re-exempting a few thousand cars every month.
Fun fact: The danish nickname for the tax authorities is "Skattefar", "Taxdaddy" - and it's the name of their twitter account: https://twitter.com/Skattefar
Disabling QIUC as parent links to unbroke things for me.
As an added benefit, you'll get de-duplication, minification, inlining (with fallbacks) and, with a little work, image-spriting thrown in almost for free.
If you want to play around easily, take a look at https://github.com/assetgraph/assetgraph-builder
(And I managed to check it within my first month there. My boss kindly let me know the difference between a client saying emergency and a VP saying so....)
Prometheus implemented the Gorilla-bits (see https://prometheus.io/blog/2016/05/08/when-to-use-varbit-chu...) and reports getting down to 1,28 B per sample on some workloads, though at a cost of increased query-latencies.
Slightly related to yesterdays' new of Danish-origin Unity raising capital https://news.ycombinator.com/item?id=12087336
> Zendesk is also Danish originally, Tradeshift is, Podio.. they all end up leaving because the market opportunity in Denmark is very small (6mio) and there isn't easy enough access to talent when you need to scale up
Podio mostly had a sales-office in SF; most development was in Copenhagen (until Citrix moved most of it to North Carolina half a year back or so)
While I'm not aware of their legal statuses, both Zendesk and Tradeshift has non-trivial amounts of development in Copenhagen.
Realm moved (and was part of Ycombinator, even) and then moved back to Copenhagen.
Falcon.io always had most of their development in Copenhagen and only really moved sales elsewhere.
It generally seem to me that they take a few semesters stateside to get known/funding/... and them move back. I've heard access to talent, employee mentality and "founders' wanted kids to grow up sane" amongst reasons for moving wholly/partially back.
I see that there's a bunch of `nix-whatever` tools around, but even their names aren't much sensible.
I'm not in doubt that nix is technically superior to homebrew, but UX-wise it's at least been a disappointing experience for me.
I've been pondering about that too (mostly something with having a service worker drawing each char on a canvas, uploading that to a server), but keeping track of OS/Browser/vendor/font-setup/... (let alone getting it all out of the browser) makes it pretty hairy to get right.
I use the fragment-identifier for that, ex http://charcod.es/#foobar. Also, check https://github.com/msiebuhr/charcod.es/blob/master/http-pub/... for doing searches directly.
Last first: Getting enough competent people to whatever you have. Just getting people that knows the difference between rm -rf / and rm -rf ./, not to plug both ends of a cable into the same switch/router, ... can be quite hard. If you have a premium product running on a few hundred machines, AWS doesn't actually eat that much margin compared to having your own 24/7 staff & all that entails.
And when the company then decides to open up "somewhere over in that big asian market", you've got to do it all over again. You can get a lot done with "remote hands" and whatnot, but again - something that eats your margin, just as AWS does...
I think it's safe to say that he's forgotten more about C/kernel/low-level/... programming than HN'ers will ever know.
(TL;DR: Yes, he thought things through and are ntimed is implementing a few new tricks.)
... until someone pointed out that building a submarine with ballistic missiles and playing with it in Russia's back-yard probably is a very bad idea.