OskarS

42 ms·

511.
by OskarS 5y ago
This one is interesting: "Take pleasure in writing more code". I agree with the author's reasoning that the number of lines of code you write is meaningless and not something you should hold up with pride, but there is a flip
512.
by OskarS 5y ago
I'm curious about this as well. And it's not just GC: just allocating memory is not real-time safe unless you're using something like a bump allocator. Lua seems very much like the wrong language for this.
513.
by OskarS 5y ago
I’ve seen packages that do ”internet-detection” by calling out to icanhazip.com, and I just thought that was so irresposnible. What if your package got popular, how much money are you costing the hoster? For services like this, people just
514.
by OskarS 5y ago
Honestly: it's hard to take these kinds of post seriously when the domain is listed as dailymail.co.uk.
515.
by OskarS 5y ago
I think he's saying that inside of the loop in FizzBuzz, it should look like something like this (Python-esque pseudocode, assuming for a second print() doesn't add a newline automatically): if x % 3 == 0: print(&quo
516.
by OskarS 5y ago
// this shows a persistent value FizzBuzz grid // whatever cell you pick is remembered for a month Wait, what?
517.
by OskarS 5y ago
In the illustration of the stack of things it replaces, it includes "Unix". Which is... you know... a claim one could make.
518.
by OskarS 5y ago
I don’t see this as a bad thing. Suburbs have large negative externalities, disincentivizing people from living in them as opposed to dense urban centers seems like a fine policy to me.
519.
by OskarS 5y ago
I’m sorry, but I don’t buy the theory that burning out your most talented engineers until they quit in an effort to put out an app update 6 months early (or whatever) is a healthy long-term strategy.
520.
by OskarS 5y ago
”git clean” sort-of works like this. It errors out unless you explicitly specify if it’s a real run or dry run.
521.
by OskarS 5y ago
One recent favorite of these mentioned in the article is ORCA [1], which is really an incredible little thing. It is essentially a live coding environment for generating MIDI you can send into a synth, with some influence from 2D esoteric l
522.
by OskarS 5y ago
The loop counter is signed even if param is not, so i++ could overflow. fwrapv is a compiler flag, it is not part of the standard: it is a flag that mandates a certain behaviour in this case, but in standard C, the loop variable overflowing
523.
by OskarS 5y ago
I’m not sure I agree. If signed overflow is UB, loops like this can be optimized the hell out of. The most obvious way would be to unroll it and eliminate the loop (and loop variable) entirely, but you can also do things like vectorize it,
524.
by OskarS 5y ago
Assuming you defined signed integer overflow to follow two’s complement rules (the only reasonable interpretation other than UB), it would still be a guaranteed loop count of 16. (EDIT: i’m a dumbass, this is obvs not true. disregard this p
525.
by OskarS 5y ago
Ah, that makes a ton of sense. Thanks!
526.
by OskarS 5y ago
I get that the CVE is a joke, but are you saying the paper is as well?
527.
by OskarS 5y ago
Haven't looked into this paper deeply, but this reads very strange to me: > This paper reports on the discovery of an accidental arbitrary code execution vulnerability in Marvin Minsky's 1967 implementation of the universal Tur
528.
by OskarS 5y ago
Great article, just to add one thing: conditional branches can seriously mess with the compiler's ability to optimize, especially the ability to auto-vectorize. So even if a never-taken branch is more or less free when the CPU executes
529.
by OskarS 5y ago
I would bet that if you compare it to a traditional server-client database (which functionally does essentially the same thing: you send it a query over the network, and get a result back), the overhead is probably massive. This is a very c
530.
by OskarS 5y ago
Those last two are actually Swedish place names already.
531.
by OskarS 6y ago
The C programming language does not provide any guarantees that tail calls will be optimized out in this way. Compilers are free to do it if they want to and it doesn't violate the "as-if" rule, but they are neither required
532.
by OskarS 6y ago
Yeah, don't worry about it. People learn new things all the time, I didn't mind writing the comment :)
533.
by OskarS 6y ago
I don't see people using the specific colors very often, it's more like "that function is colored differently" or "this language doesn't have colored functions". When used like that, it's a really use
534.
by OskarS 6y ago
If you're not, here's the link [0]. It's a pretty influential post, it's introduced whole new terminology of "colored functions" into tech jargon that's starting to become reasonably commonly used. You sho
535.
by OskarS 6y ago
> The fix is easy, just make MUSTTAIL expand to nothing in debug builds. That wouldn’t work. The final call is a recursive call to dispatch, if that is not a tail call it will blow the stack instantly.
536.
by OskarS 6y ago
My of these is the block dedicated to western musical notation.
537.
by OskarS 6y ago
Or even just search the pharmacy website to see if that branch had it in stock? I would think something like this would be the most likely culprit.
538.
by OskarS 6y ago
It would be hard for him to be clearer: > With the main point of Rust being safety, there is no way I will ever accept "panic dynamically" (whether due to out-of-memory or due to anything else - I also reacted to the "floa
539.
by OskarS 6y ago
I have no dog in this fight either way, I'm just very curious about the answer: if something like 30-40% in a Go executable that clocks in at more than a 100 megabytes is not taken up by either symbols, debug information or the pclntab
540.
by OskarS 6y ago
Here's what SQLite has to say about the matter in their article "How To Corrupt An SQLite Database File" [0]: > 1.2. Backup or restore while a transaction is active > Systems that run automatic backups in the background

More ›