That actually hasn’t been my experience of programmers’ behaviour. There are many developers who can’t be bothered to set up tools like IDEs, intellisense, debuggers, etc. which would definitely make them faster after the initial setup. I can easily believe it’s the same for AI.
That said, it does seem silly to require you to use it.
Sure, but I don’t think that’s an excuse for things like global hotkeys not working.
It’s a very heavily gamed benchmark. The most frequent issues I’ve seen are:
They’ve finally started labelling stupid submissions with “contentious” labels at least, but not when this study was done.
They chose an “optimized” set of algorithms from “The Computer Language Benchmarks Game” to produce results for well-optimized code in each language.
Honestly that’s all you need to know to throw this paper away.
Stop linking this, please! Any benchmark where Typescript and JavaScript are different is trash.
Wow that’s kinda crazy. My work is the opposite - we’re banned from using AI. Why is nobody in the sensible middle?
0.1f64 + 0.2f64 != 0.3f64
It does if you round it to the nearest penny.
Encoding in assumptions about a fixed amount of supported currencies in a system is broadly speaking not a good idea
Most sensible programming languages allow enums to be non-exhaustive.
Basically it uses bind mounts instead. See this page for details.
I haven’t actually used (since Plan 9 is dead) and I doubt it covers every use case for symlinks (e.g. this wouldn’t let you commit them to a git repo), but I really think the benefits of symlinks not existing at all would far outweigh the effort of having to think of alternative solutions.
Sadly we don’t get to live in that alternative history now… :-/
Double is not perfectly precise. It is quite literally a function that calculates what the value should be. There are converters to show the drift: https://www.h-schmidt.net/FloatConverter/IEEE754.html
$40.01 is literally stored as 01000010001000000000101000111101 in a float type, which is literally stored as 40.009998321533203125. The margin of error goes up the larger the number.
No you’re fundamentally misunderstanding what’s going on. Float isn’t “storing 40.01 but imprecisely”. That’s like saying an integer “stores 1.1 but imprecisely”. Floating point can’t represent the number 40.01. But that doesn’t matter because 4.0009999999999998 is easily accurate enough for any real world use.
The story of Ariane 5
This was caused by converting an f64 to i16 which caused an overflow and hardware exception. Irrelevant.
How a Minor Calculation Error Cost Intel Half a Billion Dollars
Hardware bug. Irrelevant.
Wikipedia
Literally says “The failure to intercept arose not from using floating point specifically”
and asking the stock exchange
I’m not talking about stock exchanges. Obviously they have extreme requirements. For most normal businesses and people f64 is fine.
You’re repeating dogma without thinking about it.
Yes you can. You’re vastly underestimating the size of an f64. Give me a concrete example of a money operation that fails with f64 (for normal companies; assuming you aren’t a stock exchange or Visa or whatever).
Enums are not a good idea for the currencies either.
Why not?
I guess this might be hard to understand if you’re asexual but my point is that young boys (and maybe girls) aren’t “stumbling over porn”. They’re seeking it out.
If this was only meant to prevent stumbling over porn then the existing “are you over 18? [Yes] [no]” checks would be perfectly fine.
I do wonder if there is any study backing up my idea that porn is not harmful, it’s refusing to talk about what is healthy and what is not in a relationship and modeling bad interactions that is harmful.
Yeah maybe… Porn doesn’t even try to depict normal relationships so I don’t think it could really be distorting them, unlike films or creepy influencers like Andrew Tate.
A f64 is a double, floating point precision type, aka not precise
f64 is perfectly precise.
The correct format to store money in? A string
Lol ok.
$3.99999999898998888181
If only we had this thing called rounding…
Why? It sounds like you are under the common and false impression that you can’t use f64 for money.
The Plan 9 solution looks better to me. At the very least if you keep them then paths should be resolved lexically. I think most people are under the false impression that they are resolved lexically (i.e. foo/bar/../baz and foo/baz are the same).
But IMO it’s better just to not have them and use another solution where you might have used them.
The objections to symlinks are not academic. They have real world flaws.
You used to need admin or something like that. It’s only since about 2017 that they are available to normal users by default.
Or giving in. Symlinks are a lazy hacky mistake. The original Unix authors knew it and tried to fix it in Plan9, but I guess now we’re stuck with that mistake forever. Even WASI supports symlinks.
Honestly none of those “gotchas” sound at all surprising to me. A currency enum and f64 for the amount will cover 99.99999% of use cases. u64.u64 fixed point if you really need it (you probably don’t).
Try dates/times. That’s serious pain.
Realistic more like. Half of the petitions are dumb, so they’re already conditioned to ignore them. And this one is literally something that just happened. No way they’re repealing it immediately.
Best case they roll back some stuff in like 10 years. I read a BBC article about it though and in the “criticism of the act” section they only had quotes from people saying it doesn’t go far enough! So I wouldn’t hold your breath.
It’s barely transpiled. There are a couple of features that involve actual code generation - enums and namespaces (which are almost never used), but the vast majority of it is just stripping the type annotations so the performance will be 100% identical.
It’s like having “Python” and “Python with type hints” as separate languages and claiming there is a big speed difference between them.