Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
temac
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
121.
▲
by
temac
4y ago
If it was just for aesthetics, you could have just a discreet manual release. Anyway, you don't have "a discreet manual release" on actual implementation of that crap, so yeah that's the point: you could and you should h
122.
▲
by
temac
4y ago
3 - The instruction set is made of fixed length instructions TBH there are various mostly-Apple/TSMC-"exclusive" tricks too, for why their chips are better than the others: A - On Apple Silicon, pages are larger, but not too
123.
▲
by
temac
4y ago
Expected by who? Those who have access to private info? As far as I'm concerned, I don't see why I should expect anything less than 100% usage if a vendor does not warn me otherwise, and countries exists where mandatory warantee i
124.
▲
by
temac
4y ago
Does it still need to be allowed by specific chipsets, though ?
125.
▲
by
temac
4y ago
IIRC Intel "consummer" parts are qualified for 3 (or 5 ?) years of usage at a 30% duty cycle (and you might not find that figure publicly, but honestly you should, and intel should be mandatted to publish it). Now that is likely n
126.
▲
by
temac
4y ago
I love how only some are providing the protection of not being fired for following the law. Can they order you to organize a coup, some terrorist acts, or a murder in the others?
127.
▲
by
temac
4y ago
If you exclude everything that does not go into your direction and make the hypothesis that a poor architecture would have risen and then would not have been replaced, you conclude that "everybody" would use it?
128.
▲
by
temac
4y ago
It was a poor architecture though and if not by AMD64 it would have been killed by something else more in line with traditionnal high perf superscalar. Maybe even just Arm.
129.
▲
by
temac
4y ago
I expect zen4 on laptop to be quite energy efficient, but we will see.
130.
▲
by
temac
4y ago
> Intel has tried to move away from x86 three times already Also, they tried to move to other ISAs they owned. Trying to move from their position to 3rd party or open ISAs would make even less sense.
131.
▲
by
temac
4y ago
> Even M1 macs (I have one and love it), while powerful, just can’t hold a candle to a workstation class machine. My M1 Pro is faster in some workloads than a small Dell tower sold as a "workstation". Of course I could buy a hu
132.
▲
by
temac
4y ago
Using unitialized values is UB. Going back to naive pointers is a lost cause because compilers have started to do crazy optims (not even currently allowed by the standards...) like origin analysis. You can't steal that toy from the peo
133.
▲
by
temac
4y ago
Current compilers don't "tell you to stop". They silently transform your program into complete garbage without even causality restraints. The sanitizers can help but they are merely dynamic when the dangerous tranformations a
134.
▲
by
temac
4y ago
Undefined behavior is probably the worst way we can imagine to define constraints usable by optimizers. Sad that major languages and implementations went this way.
135.
▲
by
temac
4y ago
You don't need billions to be a private leader. Or you shouldn't.
136.
▲
by
temac
4y ago
Some of the bugs and ergonomics problem you describe seem dangerous. The regulators should come in and ban those cars until they are fixed.
137.
▲
by
temac
4y ago
Interesting but I'm not sure about the relevancy to the above comment. On a sidenote, it has weird claims: > obviating the need for ownership type systems or other compiler approaches to fixing the type-safety of use-after-frees. Th
138.
▲
by
temac
4y ago
That does not "solve" plugins. That does not allow bugfixes in libraries. Edit: and worse, that's introducing plugin like problems in code that does not even use plugins. Next idea?
139.
▲
by
temac
4y ago
A thing that does not exist, still is leveraged to build whole distros, and its too high stability resulted in the creation of Carbon.
140.
▲
by
temac
4y ago
> it’s UB to take the address of a parameter via any mechanism other than explicitly taking the address - which a compiler obviously sees, and because it’s UB the compiler optimizes is free to assume no one is taking the address. I don&#
141.
▲
by
temac
4y ago
> On ext4, a file of 160 bytes or less (and no xattrs) can be stored inline in the inode[1], so the whole thing takes up 256 bytes (plus 8 + [length of filename] for the directory entry). It can if you enable an option that is not widely
142.
▲
by
temac
4y ago
The funny thing is that long mode can actually support win16 applications, and Wine does it.
143.
▲
by
temac
4y ago
The standard doesn't do that often, but it does sometimes. E.g. realloc to null which was previously defined, and is now UB :(
144.
▲
by
temac
4y ago
Debian is taking care of security maintenance of the software they ship. Now: maybe they will do a poor job of it, but that's another issue than intent; some users misdirect support requests to the upstream, but unless Debian version i
145.
▲
by
temac
4y ago
Even win 3.1 did that in a mandatory way with it dropping support for Real mode, and Standard and Enhanced were available for windows 2 already. And Windows applications of that era went through Windows API and Windows drivers, not DOS ones
146.
▲
by
temac
4y ago
Economic value has no strong meaning. When you mow your lawn yourself, does this action have economic value? If so, why is it not measured? If not, why does it have if you hire someone to do the work for you? Likewise for some jobs that are
147.
▲
by
temac
4y ago
Ironical from people working at Apple in the 90s.
148.
▲
by
temac
4y ago
Do Linux distros support hiDPI including mixed DPI (e.g. with a hiDPI laptop screen and a low DPI external one) well ? Under macOS this works really fine, under Windows this is half garbage.
149.
▲
by
temac
4y ago
What is typically needed is an easily reproducible reference CI environment. That is often approximated with a centralized reference CI environment, that is not necessarily easy to reproduce, in which case it is only instantiated very few t
150.
▲
by
temac
4y ago
The Windows default can cause problems because of simple logic bugs. The Unix default can cause unsolvable problems because of races between threads. You should use CLOEXEC everywhere. Except you can't because you are using libraries.
More ›