Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
grandinj
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
91.
▲
by
grandinj
5y ago
Natural gas power plants are relatively modular, and we can chain together units to make a bigger power plant. There is no such equivalent modular unit for petroleum processing. Each plant is highly customised to deal with a specific mix of
92.
▲
by
grandinj
5y ago
It is an enormously complex factory with a high probability of going boom if you do something wrong, so not really, no.
93.
▲
by
grandinj
5y ago
The company I work for is happily delivering Java Swing desktop apps every day. Works great, easy to debug, tons of open-source components to plug in when we need, sufficiently performant, thoroughly battle tested. And these are medium upda
94.
▲
by
grandinj
5y ago
I use thunderbird every day, and it just works. Admittedly, I just do basic stuff with it.
95.
▲
by
grandinj
5y ago
I gave talks at the Libreoffice conference in 2019 https://www.youtube.com/watch?v=QnBIeeBZf70 and in 2021 https://www.youtube.com/watch?v=VbL6mXXnFdo&list=PL0pdzjvYW9...
96.
▲
by
grandinj
5y ago
Counterpoint: I do a lot of perf work on LibreOffice, which makes extensive use of exceptions, and I have never ever even seen the exception throwing show up on a profile, let alone become a problem. I think this paper started with a conclu
97.
▲
by
grandinj
5y ago
LibreOffice is almost entirely C++, except that there are some extensions written in Java (and some written in python) I say almost, because we still have some QA code used for unit tests that is Java.
98.
▲
by
grandinj
5y ago
Speaking from experience, convincing management is a long-haul process. It is needs to be repeatedly brought (but gently). Forward links to success stories, provide counter arguments to FUD (but again, gently!) I say gently because it'
99.
▲
by
grandinj
5y ago
That's a fairly common attitude in poorer countries - there is an expectation that if you are wealthy, you have (at the very least) an obligation to provide employment.
100.
▲
by
grandinj
5y ago
It depends on how you process data. I got used to reading a lot and being comfortable with not retaining a lot. I just keep reading more stuff and eventually it sticks.
101.
▲
by
grandinj
5y ago
So they are using the same strategy as Erlang (partitioned heaps), with a nice twist of adding hierarchy. That is great, but runs into the next problem with concurrent programming - shared data - where, for performance, you absolutely have
102.
▲
by
grandinj
5y ago
Because so far, no-one (within the US legal system) has come up with a formulation for "monopoly" and "market" that does not have (a) unpleasant side effects for businesses that would normally not be considered monopolis
103.
▲
by
grandinj
5y ago
Except when stuff goes wrong. Then gradle is a right PITA because debuggability is essentially zero. And periodically a new version of gradle will break something non-obvious deep in your dependency tree.
104.
▲
by
grandinj
5y ago
You don't need __lots__ of uranium. The cost of uranium for running a nuclear reactor is a rounding error in their overall costs.
105.
▲
by
grandinj
5y ago
Pretty much most circuits are non-linear, for real-world circuits "linear" just means "linear within normal operating range"
106.
▲
by
grandinj
5y ago
lots of circuits will fold higher frequencies down into lower frequencies (but at lower energy). If you can generate enough energy, you can push enough energy into other circuits that they saturate (reach the end of their working range) and
107.
▲
by
grandinj
5y ago
To a certain extent yes, but the largest obstacle is simply that, until rather recently, the core python team was hostile to including complex stuff like a JIT into the main python interpreter codebase.
108.
▲
by
grandinj
5y ago
Much more likely that the standard optimism that runs through people when they are starting new projects lead them to dramatically underestimate the difficulty of the project - which ended up being "design a new sub from scratch"
109.
▲
by
grandinj
5y ago
And by rejecting patches that don't match up with "your way" you risk of alienating talent and resources that could have improved your project.
110.
▲
by
grandinj
5y ago
Unfortunately the primary maintainers of GIMP basically have an attitude of "we want to do it our way, and at our pace", and are not willing to accept any patches outside of that pattern. Which is both a blessing and a curse - on
111.
▲
by
grandinj
5y ago
I guess people's experiences are different :-) I find exceptions to be a perfectly fine error handling mechanism. I certainly prefer it to cluttering my code with explicit checks for return codes and such like.
112.
▲
by
grandinj
5y ago
On the other hand ( ) they solve a handful of use-cases really really well. ( ) if you are writing relatively decent C++, most code is pretty much exception safe already ( ) lots of abstractions are dangerous when mis-used ( ) they are suff
113.
▲
by
grandinj
5y ago
A more likely explanation is simply that the average age of a nuclear plant has been increasing because the build rate is so low.
114.
▲
by
grandinj
5y ago
Oracle does this too, so do some other databases. It's quite a natural optimisation.
115.
▲
by
grandinj
5y ago
i run up to about 500 threads on my Java app with ease, with about 1/3 of them pumping significant data (think stereo streaming audio type data). I started writing some fancy asynch code, but on checking with a profiler, the thread ove
116.
▲
by
grandinj
5y ago
Regular exercise seems to be key with my friends. Which means building up a set of exercise type things you like doing and finding groups of people who also like those things.
117.
▲
by
grandinj
5y ago
I built a sealed box around a Sony 15 inch car speaker. Does a really nice job and didn’t need any theory because sealed boxes are inherently more tolerant.it’s a cube about 2 and something foot on a side. Knocked it together with nails an
118.
▲
by
grandinj
5y ago
Then you should absolutely not be running. Just walk for 10 mins.
119.
▲
by
grandinj
5y ago
It's more flexible, in that I can ignore all sorts of other commits that have no bearing on the bug I'm chasing. Effectively, I am doing a manual implementation of displaying a "timeline" of commits that apply that code.
120.
▲
by
grandinj
5y ago
What I do, is I run loop like (1) git blame <file> (2) git blame <uninterestinghash>^ <file> which tells blame to go back to before the hash and do the blame. I run that loop repeatedly, picking the most recent hash each
More ›