Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mickeyp
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
91.
▲
by
mickeyp
11mo ago
I had one of those as a kid. Great watch. Reading the wikipedia page for it may make you rethink that thought though :(
92.
▲
by
mickeyp
11mo ago
1x1 pixels for padding and aligning? That came later. Your memory is off. In the 90s, sites did kinda look like that.
93.
▲
by
mickeyp
11mo ago
You are talking about low level stuff like syncing to the filesystem; that data is journalled and ensuring atomicity is maintained and I am in actual fact not. Dislocating DML from the code that triggers it creates many problems around ensu
94.
▲
by
mickeyp
11mo ago
For small oltp workloads the locking is not going to be a problem. But stuff that holds the write lock for some measurable fraction of a second even will gum things up real fast. Transactions that need it for many seconds? You'll quick
95.
▲
by
mickeyp
11mo ago
"performance optimisation" --- yeees, well, if you don't care about data integrity between your reads and writes. Who knows when those writes you scheduled really get written. And what of rollbacks due to constraint violation
96.
▲
by
mickeyp
11mo ago
Edit: disregard. I read it as he'd done it and had contention problems. I mean it's not if he's got lock contention from BUSY signals, now is it, as he implies. Much of his issues will stem from transactions blocking each oth
97.
▲
by
mickeyp
11mo ago
These are my PRAGMAs and not your PRAGMAs. Be very careful about blindly copying something that may or may not match your needs. PRAGMA foreign_keys=ON PRAGMA recursive_triggers=ON PRAGMA journal_mode=WAL PRAGMA busy_tim
98.
▲
by
mickeyp
11mo ago
Edit: disregard. I read it as he'd done it and had contention problems. You can't. You have a single writer - it's one of the many reasons sqlite is terrible for serious work. You'll need a multiprocessing Queue and a wr
99.
▲
by
mickeyp
11mo ago
I mean, you're not wrong, and that is one way to solve it, but the whole point of a sensibly-designed WAL -- never mind database engine -- is that you do not need to commit to some sort of actor model to get your db to serialise writes
100.
▲
by
mickeyp
11mo ago
Indeed. Everyone who uses sqlite will get burnt by this one day and spend a lot of time chasing down errant write-upgraded transactions that cling on for a little bit longer than intended.
101.
▲
by
mickeyp
11mo ago
SQLite is a cracking database -- I love it -- that is let down by its awful defaults in service of 'backwards compatibility.' You need a brace of PRAGMAs to get it to behave reasonably sanely if you do anything serious with it.
102.
▲
by
mickeyp
1y ago
Last time I checked, writing efficient, contention-free and correct parallel code is hard and often harder than pulling an algorithm out of a book.
103.
▲
by
mickeyp
1y ago
It is so sad to see so many people -- including the article, to an extent -- and also people in the comments cast shade on this distro and the people who may try Linux either for the first time, or perhaps one more time, because they tried
104.
▲
by
mickeyp
1y ago
[flagged]
105.
▲
by
mickeyp
1y ago
Emacs can easily work with non-posix tools. Many people use ag, ripgrep, or ack in lieu of grep. You change the command string Emacs uses for finding and grepping to your tool of choice.
106.
▲
by
mickeyp
1y ago
What? Emacs has eglot built in. It has had native grep and find stuff for decades . https://www.gnu.org/software/emacs/manual/html_node/emacs/Gr... You can change the exec-path to point to your cro
107.
▲
by
mickeyp
1y ago
The knocks against Emacs feel unwarranted. It has plenty of colour; it has mouse support, even in the terminal, but not all terminals support it, so it's optional. It also runs in a GUI with, you know, image support and whatnot. You ca
108.
▲
by
mickeyp
1y ago
False equivalence. That the creators of various PHP blogging platforms sucked at security does not invalidate the poster's point that a self-hosted CMS with a simple comment system is indeed much simpler and easier to reason about.
109.
▲
by
mickeyp
1y ago
Yeesh. "Those darn 40+-something millennials and their differing tastes!" Rock 'died' because it's been around for 50 years; were the favourite of boomers who ensured it always had air-time; and now they're out
110.
▲
by
mickeyp
1y ago
Seconds. I mean, something on the order of that, anyway. Fast enough to iterate but I mean it's still the weakest link in the iteration chain of course.
111.
▲
by
mickeyp
1y ago
Good to know, thanks! Now that I 3d print (apropos hobbies with infinite depth...) I would probably just CAD design and print my own instead, but I've come to accept the limitations, such as it is, of the moonlander's tenting desi
112.
▲
by
mickeyp
1y ago
> I switched from a Moonlander to a UHK, and the programming time is ~instant. You click flash and in 1-2 seconds it's done. For the Moonlander you have to download the firmware, find the file, drag and drop onto the flashing tool,
113.
▲
by
mickeyp
1y ago
That assumes the OOM killer kills the right thing. It may well choose to kill something ancillary, which causes your OOM program to just hang or misbehave wildly. The real danger in all of this, swap or no, is the shitty OOMKiller in Linux.
114.
▲
by
mickeyp
1y ago
Some of us use triple dash to indicate the same thing. Like LateX. You should add that too.
115.
▲
by
mickeyp
1y ago
Care to show me a job board bursting at the seams with Delphi jobs?
116.
▲
by
mickeyp
1y ago
Uh-huh. There are zero -- sorry, nil -- Delphi jobs on jobserve in the UK. That is one of the leading job sites in the UK. Zero. There are 282 jobs with python in the job description.
117.
▲
by
mickeyp
1y ago
Yes, that sounds like a Delphi developer alright. I worked with Delphi personally and professionally for many, many years. You were at the precipice of unemployment in the 2000s if you used it then. To do it now? You're like a looney t
118.
▲
by
mickeyp
1y ago
Right, but it instantiates it _once_ on module load! That is the point I am making; nothing else.
119.
▲
by
mickeyp
1y ago
I wrote the link and yes it does. Module evaluations reify {}, [], etc. once. That is why people keep making subtle bugs when they do `def foo(a=[]):` unaware that this will in fact not give you a brand new list on every function call. Fact
120.
▲
by
mickeyp
1y ago
All this lather about doing it the UNIX way, whilst neglecting to point out that the old tooling was far worse. "Do one thing well" implies it was done well to begin with. DNS: Can you from memory recite how name lookups work on L
More ›