frou_dh

Hobby-horse trolling detected.

Having a zero Easter Egg policy is simply the only thing that makes sense, because there's no guarantee that something slipped in by an individual employee who thinks it's funny or tasteful... is actually funny or tasteful.

The dodgy hardware doesn't reflect well on the Google/Pixel brand, that's for sure.

That said, I'm fairly happy with this because my 6a just sits around as an Android test device. Probably only has tens of battery cycles on it and might not ever reach the 400 cycle count where they've deemed this upcoming software nerf needs to kick in. So a free $100 and still keeping the phone is fine by me.

https://i.imgur.com/4wpSMAW.png

As a kid, that look felt somehow off to me because I could sense that it was at some level "fake". The various magazines at the time could be kinda wooly on the subject and imply that the power of the SNES was rendering the characters etc in realtime (rather than it essentially being flipbook animation).

> Stronger expected lifespan

I think Emacs is a good example of the Lindy Effect. It's going to continue being alive for a long time because it's already been alive for a long time.

https://en.wikipedia.org/wiki/Lindy_effect

That's disappointing. From following 37signals, I honestly thought Mr. HH had better design sensibilities than a TUI-obsessed /r/unixporn dweller. Look at the screenshots - there's like half a dozen different attempts at primitive pseudo line-drawing, all mixed into the same pot. Overall it just looks horrendous.

Talking of Emacs, there is a very well designed DAP-based debugger available as the 'dape' package.

https://elpa.gnu.org/packages/dape.html

The way it's designed (incl. having no dependencies) suggests that they will be angling for it to be included with stock Emacs at some point.

It should stay true to itself and not do it at all.

Sigh - all languages needn't converge into Grey Goo.

Let's take a look at SvelteKit. Huh, it has zero to say about the database? And this is the first framework that comes to mind as equivalent to Rails? Sheer insanity

Something that seems quite common on the false-negative side is type names not being highlighted at all when they are the names of user-defined types, even though they're being used in type positions in the code. Dumb highlighting will just have a fixed list of type names it knows about, because it is not as aware of the positional aspect of usages.

It's so nice when an editor can do completely accurate syntax-highlighting for a language. I think there is a subconscious disturbing effect when being presented with false-positive and false-negative colouring here and there, as traditional "good-enough" hacky syntax highlighting tends to result in.

Cuis Smalltalk seems to be the keeper of the old Smalltalk experience:

https://cuis.st

https://cuis.st/features

Pharo is like enterprise-grade, bells and whistles galore.

Are you doing a Comic-Book-Guy impersonation?

Given an eval primitive function that's a black-box, using it does seem somewhat similar to the use of a macro, in that a kind of "double evaluation" occurs (First, eval's argument is evaluated. Then the result of that is evaluated).

When a macro is used for any given purpose, what happens is a bit more general because it first "does something with" its argument (rather than necessarily straight-up evaluating it). Then the result of that is evaluated.

Apparently timeout(1) is part of GNU Coreutils. I wasn't sure after reading whether it was part of Bash itself.

Compared to something with automatic bidirectional sync between all devices, something where one has to manually commit/push/pull a new/edited note feels archaic.

I remember Matz gave a presentation touching on how Ruby was inspired by Lisp and particularly Emacs Lisp, which was the one he had access to. You still can feel a similarity up to now, with the single big old dynamic namespace where you can monkey-patch anything if you feel like it.

Yes, when navigating a repo's files on an older computer, I noticed that it took an incredible length of time to rehydrate pages or whatever it's doing.

I would guess it's because we want the flow of information to start in the top left, and overall more conversations started with the other party messaging you (due to automated SMS).

> I suspect this is the real reason Clojure was created, I bet Rich was just really bored.

Well he spelled out the motivations in numerous early presentations so I don't think he'd take kindly to the implication they were BS.

I remember a funny quote along the lines of, he felt the concurrent software he'd already written in C++ and Java had required "He-Man" levels of perspiration to actually get correct.

From hanging around Deno's official Discord, Reddit, etc, I get the impression that there are simply not that many people using it.

I doubt they are making much money from the public-facing Deno Deploy product, and are probably reducing its number of regions because those who are using it are mostly just noodling around on the free tier.

I think someone said the definition of legacy code is code that makes lots of money.

Because it's a massively competitive space, and being passably good ("Hey guys, the toolchain and these libraries do actually run on Linux. Also we have XYZ Working Group.") is not sufficient to get peoples' attention.

Being able to use the features of a debugger to understand a problem in a single run, as opposed to editing the code adding/removing print statements and (recompiling+)rerunning the program over and over again.

There's been some kind of macho attitude dispersed wherein it's uncool to use good tooling, so a lot of people don't even learn how to use debuggers properly.

https://kapeli.com/dash for MacOS supports man pages just like any of its many other documentation sources. Simply type `man:foo`. Absolute hall of fame app IMO.

Accuracy issues aside, a draw that I feel towards using e.g. ChatGPT is that the information is displayed in a more consistent way. When using a search engine and opening a bunch of the results in tabs, I have to reorient myself to each site because they all have different visual designs.

As ever, there's no need to guess what's happening when one has a Profiler on hand.

2019: https://www.macworld.com/article/233056/ios-13-and-ipados-13...

Nice article, bookmarked.

For the "Mechanically name join tables" point, I would at least put a tiny bit of effort into their names, rather than zero. For example, using a naming convention to make that kind of table instantly recognisable, e.g. 'person_x_pet' instead of just 'person_pet'.

"Vibe coding" seems like one of those things where there's way more people complaining about the concept than there ever were people actually promoting it in the first place.