1,471 karma · joined January 15, 2012
[ my public key: https://keybase.io/rohansingh; my proof: https://keybase.io/rohansingh/sigs/FYqfP0wJErPun-vsVRQ2fAEqahFzGh-6AGFTFN5MRYE ]
--gc:stack
--header:"nim.h"
--os:standalone
--noMain
--genDeps
In the end I got Nim code to run and was able to do a "hello world". As a hack I also used -d:android to trigger some conditionals that reduced the reliance on various dependencies. But it wasn't enough to be usable, and it was a bit unfortunate to have to do that.Looking at those projects you linked though, clearly I didn't try hard enough! Great to see that people have had success.
In practice, even once I was able to compile basic Nim, there were a lot of glibc and other POSIX dependencies for any of Nim's standard libraries, some of which weren't available in ESP-IDF.
That's totally fair, but many of those dependencies aren't available when compiling to JS either, though, so I was surprised. In the end, delving into the code I found that a lot of stuff was gated behind the equivalent of "platform=JS" switches throughout the stdlib. It seemed like adding support for another platform would be a major pain.
This was all preliminary investigation and I didn't reach out to the Nim community, so perhaps I missed something. Maybe this kind of portability isn't even a goal for Nim. It would definitely be nice to have, though.
The first couple drafts took forever to figure out, and I got a bunch of stuff wrong. This guide would've saved a ton of time back then.
Examples include distributed systems, realtime software, embedded programming, network programming, etc.
However, if drivers all started going at the normal speed and regularly tripping broken signals, it would absolutely destroy the system. When a train's emergency brake is tripped, it takes tens of minutes to reset it and get the train going again. If that was happening at every faulty signal on a daily basis, the system would grind to a halt.
Really the only fix is dealing with the signals. But that's extremely difficult because they haven't been regularly maintained and are very old. Most of them use mechanical timing systems and other insane things that nobody has built parts for. There's no particular reason to believe that "changing them back" would go any better than the botched rollout of the initial change.
From both my experience and that of folks I've spoken with, the last year or two has been quite good for us. That said, you're probably much better off financially if you accepted an offer from a FAANG-type company around the same time and stuck with them.
> Betteridge's law of headlines is one name for an adage that states: "Any headline that ends in a question mark can be answered by the word no."
I'll try to do a blog post when I get the chance.
How we do things is quite different now. Check out my DockerCon 2014 presentation or our tech blog for details.
It's just cheaper and easier for us to have a lot of hardware racked and stacked and then spin it up as needed without having to worry about virtualization. Experience for our devs is pretty much the same whether they're provisioning a bare metal machine as it would be for a VM.
Median Income 25-44 $78,810
Median Income 45-64 $80,875For example, if I pay for rights to drill for oil somewhere and oil becomes obsolete, should I be reimbursed by my competitors?
The upside potential of one of these medallions was unlimited. After buying it once, you could use it to make an unbounded amount of money. Part of that is accepting the risk that it might make no money. Otherwise you're asking the rest of society to subsidize a private interest.
> Hint: > 'less' doesn't interpret escape sequences unless the -r switch is used, > so stop aliasing it to 'less -r' just because there's no colored output.
Instead you can just use `less -R` which allows colored output but doesn't interpret any other escape sequences.
Back when the only data center was in Stockholm, the only way to meet latency requirements was P2P. Now that we're a grown-up company we've disabled that and use CDN's instead.