Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
rwmj
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
181.
▲
by
rwmj
3mo ago
The press release: https://newsroom.ibm.com/2026-07-14-Arvind-Krishnas-Letter-t... With the caveat that I work for IBM but have no inside knowledge about anything important, it doesn't seem very bad to me? Overall pro
182.
▲
by
rwmj
3mo ago
Recently bought a guitar amp which came with a cursed USB-C cable: http://oirase.annexia.org/tmp/IMG_20260709_123740.jpg
183.
▲
by
rwmj
3mo ago
You've still no idea. Who is going to certify it? No auditor will certify vibe coded slop. Who will provide the indemnity for it? No insurer will touch it. It doesn't even save significant money. The cost of writing the code
184.
▲
by
rwmj
3mo ago
This is such a nonsense take. You have no idea how the companies that use mainframes actually operate. There's no world in which they will vibecode a solution.
185.
▲
by
rwmj
3mo ago
Press release: https://newsroom.ibm.com/2026-07-14-Arvind-Krishnas-Letter-t...
186.
▲
Deaths in the UK outnumber births for first time in 50 years
(telegraph.co.uk)
1 points
by
rwmj
3mo ago
|
1 comments
187.
▲
by
rwmj
3mo ago
Aarch64 dropped thumb instructions. I don't think you're going to find a single benchmark on the effectiveness of compressed instructions since it really depends deeply on both the workload and the whole system. For example, memo
188.
▲
by
rwmj
3mo ago
If you have some specific question I may be able to answer it, since I've been involved with RISC-V for over a decade, dealt with all the main companies involved, written papers, etc. but so far I see no actual question or concrete obj
189.
▲
by
rwmj
3mo ago
High performance RISC-V chips exist from Rivos, Ventana and others, and high performance variable length chips also exist in general (AMD, Intel). So in actual reality it increases complexity somewhat, but is not a problem.
190.
▲
by
rwmj
3mo ago
Compressed is necessary to reduce code size which is important for performance. A bunch of vendors have done high performance server chips which support compressed (Rivos, Ventana, some Chinese vendors), so in actual reality this was only a
191.
▲
by
rwmj
3mo ago
Yes, fixed-length instructions are easier to decode, but that also means a hard upper limit on the number of instructions that could ever be supported. Which is obviously a problem for a future-proof architecture. The rationale for this an
192.
▲
by
rwmj
3mo ago
RISC-V definitely does support instructions longer than 32 bits, starting at 48 bits (ie. 32 + 16), and going much longer. They are much easier to decode than x86 because the length is evident from the first byte. No ratified extension
193.
▲
by
rwmj
3mo ago
I'm not directly involved in the day to day activity around this, but as I understand it, it's about triaging related crashes together and associating them with prior bugs and suggesting fixes, else escalating.
194.
▲
by
rwmj
3mo ago
I broadly agree with your points except one. Requiring C (compressed) is necessary to avoid splitting the Linux ecosystem. Chips lacking C would never be able to run binaries compiled with C. There's no practical way for such binarie
195.
▲
by
rwmj
3mo ago
I wonder how it's possible for a developer to assign profit. The article mentions Uber's $1500 limit per developer per month. At work we're using an LLM to analyze Windows crash dumps, which turns out to be quite expensive
196.
▲
by
rwmj
3mo ago
I do have working arms and hands, so for the lights and fans in my house I don't need to assume otherwise.
197.
▲
The brutal, powerful legacy of Threads
(thebulletin.org)
6 points
by
rwmj
3mo ago
|
1 comments
198.
▲
by
rwmj
3mo ago
Pretty relevant because I've never seen the reason for "smart" gadgets at all. Physical switches are simply better.
199.
▲
by
rwmj
3mo ago
I ran a gitweb server which was battered by bots so I eventually had to take it down. Gitweb! You can just connect using the git protocol and download everything vastly more efficiently! In other words, they don't care at all. For t
200.
▲
by
rwmj
3mo ago
Even worse, not blocked, shadowbanned.
201.
▲
by
rwmj
3mo ago
I use a fan with an on/off button.
202.
▲
by
rwmj
4mo ago
https://nedhardy.com/2023/02/12/terminator-2-helicopter/
203.
▲
by
rwmj
4mo ago
Which bit of Europe are you talking about? Italy and Spain have AC everywhere. Further north it hasn't been necessary until very recently, and now people are fighting in shops to buy portable units and there are going to be loads of p
204.
▲
by
rwmj
4mo ago
It's not a great comparison because Germany could not hit the US mainland. Even if there had been a single giant everything factory it wouldn't have mattered.
205.
▲
by
rwmj
4mo ago
It was in Byte circa 1989-1991 & I've been trying to search for it with no luck so far. FOUND IT! https://archive.org/details/1982-10-byte-magazine-october-1-...
206.
▲
by
rwmj
4mo ago
This is great. It somewhat reminded me of Steve Ciarcia's build of a Mandelbrot-generating supercomputer from around 1990. That was also made from microcontrollers (Intel 8052 in that case).
207.
▲
by
rwmj
4mo ago
nginx might not, but some automated tool / cron job using libguestfs might. Kernel KVM has a very good record for security so it's not something to worry about, compared to (for example) lesser used drivers/filesystems or ot
208.
▲
by
rwmj
4mo ago
Because you want users to use virtualization for sandboxing without needing to make system-wide changes. That generally improves security overall. You might as well ask "why allow users to run anything at all?" since they can
209.
▲
by
rwmj
4mo ago
It's good that no leaked keys were found in the front end code but the developer wasn't able to look at the backend where, if the quality of the front end is any indication, there are likely to be many security issues. Hopefully
210.
▲
by
rwmj
4mo ago
In the thread the developer is only able to look at the front-end code. The real problem is more likely in the back-end code where there'll be hilariously bad security issues. Hopefully Tan isn't running this on the same server
More ›