veltas

10 ms·

151.
by veltas 11mo ago
It's particularly jarring to basically every site I've seen it on which is usually some serious and professional looking open source site. I wonder why nobody configures this, is this not something that they can configure themselv
152.
by veltas 11mo ago
> cheap VAXen roamed the land I'm stealing this
153.
by veltas 11mo ago
Everything they're asking for my head was just screaming the whole time "this is a web browser".
154.
by veltas 11mo ago
What I said is a very general statement that broadly applies to all civilised countries, reiterated because the parent comment was very incorrect suggesting that rights are mainly protecting citizens from their state in the US. It's s
155.
by veltas 11mo ago
Obviously the rights that the state grants are different in the US than Europe, but the rights of individuals are protected versus other individuals, corporations, and general organisations; just as they are in all civilised countries. To
156.
by veltas 11mo ago
I don't agree with that at all. If anyone else tries to infringe your rights it's either voluntary i.e. you've consented to this, or it's involuntary in which case you can sue them or the state will prosecute them on yo
157.
by veltas 11mo ago
In the quote it sounds like they're conflating veganism and vegetarianism.
158.
by veltas 11mo ago
I'm guessing in those kinds of situations it doesn't matter about the arch given x86 and ARM also aren't ISO standards. The manufacturers however should comply with relevant quality standards.
159.
by veltas 11mo ago
No overflow/carry flag impacting safe overflow checking and bignum performance, the whole conditional move history and backpeddling and state of Zicond, the system for describing feature support is needlessly complicated and just a mes
160.
by veltas 11mo ago
RISC-V has always been an ivory tower, with a lot of bad decisions they double down on. Not surprised they're rushing towards this outdated stamp of authority too.
161.
by veltas 11mo ago
Says that, but I don't agree with that. If anything it would have been less successful being picked up in discount markets if the specs weren't free for download, and I don't know what fringes they're trying to break in
162.
by veltas 1y ago
Automatically translating C to unsafe Rust is pointless, the resultant code is harder to read and there's no improvement in understanding how to get the code maintainable and safe, that requires tons of manual work by someone with a de
163.
by veltas 1y ago
I hope this experimental language becomes usable eventually, all I hear is how you have to continuously rewrite to work around the borrow checker, accept worse performance to make everything message based, or just ignore the type system and
164.
by veltas 1y ago
What is wrong with let?
165.
by veltas 1y ago
100%, life's too short. Ultra-pedantic const-correctness (vs tasteful const-correctness on e.g. pass-by-reference arguments or static/big objects) catches nearly no bugs in practice and significantly increases the visual noise of
166.
by veltas 1y ago
Yep and you can really tell on certain shades of grey when the screen is mysteriously flickering. Thanks Dell.
167.
by veltas 1y ago
Surely dithering is good enough to display 10-bit colour on a non-10-bit monitor with good colour. The banding disappears and the noise introduced by dithering should hide the lack of depth completely to human eyes. So a modern use for grap
168.
by veltas 1y ago
You're glossing over the "just rewrite everything in Rust" part.
169.
by veltas 1y ago
Not for simple collaboration or modification, which is most of what you want to do. But yes any serious development is difficult in Forth, period.
170.
by veltas 1y ago
Can't exactly change existing widespread practice so they're ready for that kind of handling.
171.
by veltas 1y ago
Have you tried collaborating with Forth? There's a lot of documented history of people doing so in industry when it was actually used, and more recently I've usually found Forth codebases approachable and easy to follow. Personal
172.
by veltas 1y ago
Not that obvious when some tax payers will pay for new energy infrastructure and then also watch their prices go up because it wasn't built near them.
173.
by veltas 1y ago
For anyone interested in this debate about working in 'secrecy' vs 'out in the open', this is the subject of the 1997 essay (and later book) "The Cathedral and the Bazaar" by Eric S. Raymond, comparing the clas
174.
by veltas 1y ago
There's no 'instead', you can remember them both.
175.
by veltas 1y ago
> Note how gcc is smart enough to detect that the expression ((0xc<<12) | 0xafe) is constant, so it can skip shifts and bitwise assembly operations and just emit the resulting immediate value at line 14. The same goes for the loop
176.
by veltas 1y ago
If you don't like him don't go to his talk.
177.
by veltas 1y ago
Should be called "Introduction to Functional Programming Languages"
178.
by veltas 1y ago
Which I think most people understood not to do themselves when they encountered their first issue with the precedence of << vs other operators in expressions they wanted to print.
179.
by veltas 1y ago
0 is guaranteed to mean 'success', although not guaranteed that it's equal to EXIT_SUCCESS, so you can always use 0.
180.
by veltas 1y ago
I feel the same way about C/C++ having default return of 0 in main() only.

More ›