HNHacker News
TopNewBestAskShowJobs

grandinj

1,739 karma · joined August 21, 2009

Noel Grandin, Cape Town, South Africa
submissionscomments
grandinj··on Microsoft is killing WordPad in Windows
95% of the patches __are__ bugfixing. New features are pretty rare.

We're mostly volunteers, so people implement whatever they feel like doing :-) The essence of open-source.

Come help out if you can, or sponsor some fixes with one of the LibreOffice consulting companies.

grandinj··on Unix sockets, Cygwin, SSH agents, and sadness
The root of the problem is attempting to avoid porting git to Windows properly, which leads to increasing contortions once you get past the easy stuff.
grandinj··on C and C++ prioritize performance over correctness
rsc should really know better, he has been around long enough.

C and C++ have as a basic design rationale

    "as close to machine performance as possible"

    "don't pay for what you don't use"

    "don't break backwards compatibility"
The last one is what is what is responsible for most of the issues. It would be nice to fix stuff like UB, but the reason that C/C++ is so popular and still alive is precisely because it does care more about compatibility than fixing stuff likethat.

Breaking existing code is extremely uncool for long-lived codebases.

grandinj··on Scaling to around 15K requests per second with Java
Terminating the TCP with any kind of reverse-proxy and forwarding over a local TCP port to Tomcat would get you most of the benefit with very litte configuration and is a fairly standard setup.

It plays to the strengths of both becuase the reverse proxy handles long-lived but slow connections very well, and the Tomcat server gets to have fewer, but hotter threads.

grandinj··on Intel is all-in on backside power delivery
It feels weird to me that they are not rather just laying down power layers first, then some copper, and then the logic layers.

So just build a deeper stack of layers, rather than flipping and grinding.

But probably there is a reason.

grandinj··on The teens behind the Mirai botnet
These teens convinced themselves that what they were doing was in some way "acceptable", and consequently caused quite a lot of damage.

Other teens convince themselves that some shoplifting, or car stealing, or drug dealing is "acceptable".

Why does the first group get a pass?

grandinj··on Supercentenarian records show patterns indicative of errors and pension fraud (2020)
One is rank data, the other a continuous variable. Two very different sub-fields of statistics apply to the two kinds of data.
grandinj··on Steel Threads are a powerful but obscure software design approach
Sounds like XP's (eXtreme Programming) Spike Solution
grandinj··on LibreOffice 7.5 update: A great time to jump on this FOSS productivity suite
What would you need? Python is already supported as a plugin/extension language for several years now (admittedly there have been bugs)
grandinj··on LibreOffice 7.5 Released
Compatibility improvements happen all the time on an ongoing basis. It’s just such a regular part of development that we don’t call it out anymore.
grandinj··on Inflation is falling much faster than most people know
It will be interesting to see how policy changes when oil prices do not drive so much of the economy
grandinj··on Write better error messages
Probably just me, but I am less concerned with how good my error messages are, and more concerned with trying very very hard to make the errors happen closer to the cause of the problem, rather than further away.

"Fail early, fail hard"

i.e. if I can make the error message happen near the beginning of a process, I can get away with making it a hard error.

Hard errors in the middle of a multi-hour operation tend to annoy people.

grandinj··on Write better error messages
Some developers are just lazy, and will likely need some kind of negative feedback to force them to confront their own laziness.

Which can be tricky, because the degree of negative feedback that is appropriate to the person in question can range from

"Polite one-on-one suggestion that you read the error message more than once before calling me"

to

"Full on yelling at the person in the middle of an open-plan office".

Thankfully, type II is rare, but they do occur.

grandinj··on Vogtle Unit 3 starts nuclear fuel load
No, if the rules specified that level of detail, they would probably be all right. The NRC rules appear to be higher level, and built around specifying "safety methodologies", and it's the translation of those safety methodologies to concrete (haha) level detail that gets messy.

Although to fair on the NRC, there was a case where, due to lack of experience, the contractor cast an enormous slab using the wrong rating of concrete, which then had to be removed at great expense and delay.

grandinj··on Vogtle Unit 3 starts nuclear fuel load
It's not that the rules change, it's that the rules (as written) are open to interpretation. So if you design something, get it approved, start building, then get the NRC inspector on-site to confirm, and he disagrees with your interpretation, you get to rip out that piece and rebuild it, with all the attendant delays and costs.
grandinj··on Blender: Wayland Support on Linux
> I already said: > >>and implementing client and compositor support for it. It's exactly the same as X.

Not quite the same. X11 (notably the xfree86 project which maintained things for the last decade or so), was always quite free-wheeling about allowing things. They subscribed to something similar to the linux kernels approach of "mechanism, not policy".

No, I don't think there is any conspiracy. Nor do I think they are bad people.

Nor do I think the whole thing is over-engineered. It's mostly pretty impressive.

grandinj··on Blender: Wayland Support on Linux
yes, technically you can do that.

But if you actually want to __use__ your extension/protocol with someone else, it needs to get accepted into various core libs and repositories.

....And then the gatekeepers step up and your problems start.

grandinj··on Blender: Wayland Support on Linux
X11 has always had extensions.

Every frame is perfect requires extreme amounts of coordination. Frequently multiple buffering, which increases latency and increases latency. All these are costs which most use-cases don't care about.

Under normal conditions, with display managers that don't care, frames are extremely rarely "not perfect". And when they aren't perfect they are seldom "not perfect" for more than a single frame.

This is a fine example of "the perfect is the enemy of the good"

grandinj··on Blender: Wayland Support on Linux
What you are seeing is a change in culture.

X11 was very much a "everything is a work-in-progress" culture. Experiments were fine, clients and servers could support whatever they wanted, etc, etc.

Wayland is an "opinionated" culture. Everything the core devs don't like is not allowed.

Everything HAS to fit into the "every frame is perfect" mantra. Which is ridiculous over-engineering and disallows a large number of perfectly acceptable (to end users) use-cases.

grandinj··on JavaFX 19
Not strictly consumer, rather a niche space, but we're still shipping Swing based apps, and our customers neither know what the UI toolkit is, nor do they care.
grandinj··on Health insurers just published close to a trillion hospital prices
And also...

For many years Canada (and similar countries) have relied on cutting costs by importing health care professionals from other countries. That pipeline has now shrunk considerably, resulting in the exposure of the underlying problem.

grandinj··on The fight against drought in California has a new tool: The restrictor
The Dems already have a super-majority in the california senate, so that problem has been solved?
grandinj··on Ushering out strlcpy()
the git codebase internally does this, has quite a nice library of C functions to work on them
grandinj··on Show HN: Modifying Clang for a Safer, More Explicit C++
So we don't really have strong coding standards (kind of tricky when you inherit a 10 million LOC codebase written over ~20 years), we just try to be pragmatic and improve the code where we can.

So we have a collection of plugins, see here: https://cgit.freedesktop.org/libreoffice/core/tree/compilerp...

Which verify a variety of things.

We focus on 2 things: finding dodgy code and using APIs correctly. We don't try to modify the C++ language, just restrict accidentally straying into some of the really nasty corners.

But I like to keep an eye on experiments like yours for ideas :-)

e.g.

no c-style casts: https://cgit.freedesktop.org/libreoffice/core/tree/compilerp...

use the comma-operator sparingly: https://cgit.freedesktop.org/libreoffice/core/tree/compilerp...

is your loop variable really big enough: https://cgit.freedesktop.org/libreoffice/core/tree/compilerp...

calling virtual methods from destructors is dodgy: https://cgit.freedesktop.org/libreoffice/core/tree/compilerp...

grandinj··on Show HN: Modifying Clang for a Safer, More Explicit C++
In the libreoffice project, we have implemented some of this eg. no c style casts, using clang plugins, which avoids needing a custom build of clang. But always good to see people experimenting in this space!
grandinj··on Let's Try Gnome Boxes
Excellent! So good to see people building easy to use UIs that get you started with stuff like this. A lot of time you just want to get something simple done and this kind of UI is perfect for that.
grandinj··on GTK: Consider dropping the X11 back end
Works well, or just barely? Because the last time I checked it still had highly annoying 500ms lag and would sometimes miss screen updates.
grandinj··on Netflix’s bad habits have caught up with it
The more entertaing version of this story goes:

IBM asks Japanese manufacturer to make 100 boards, specifying 1% failure rate.

On the day of the delivery from the manufacturer, the Japanese CEO comes to inspect the final shipment.

After doing so, he discusses the contract with his chief engineer, and the engineer mentions the failure rate spec.

The CEO nods, takes a board from a box, breaks it over his knee, and says "There is our failure rate".

grandinj··on The Problem with Slack at Scale
The original Google Chat (with the little Windows client that sat in your taskbar) was surpringly good.

And then, of course they killed it and made it a web UI thing and made it majorly worse at the same time

grandinj··on Germany has seized control of Gazprom Germania
The danger is illusory. Natural gas is more actually dangerous - see periodic fires from using it to hear things. And the amount of nyckear waste produced in the whole world is so small is doesn’t even register on any kind of “future problem” scale
← PreviousPage 3 of 16Next →