anothername12

I have warm fuzzies for way back when I coded in Turbo Pascal. Even on the 8086 I had at the time, compilation speed was incredibly fast even on midsized projects. Much faster than my day to day work with Go on an M3 Max.

I had to install it last night in DOSBox-X and compile the Breakout example project. The warm fuzzies are justified.

Go mod inadequate for Go projects?

We have giant Go monorepo at work. Bazel build. The ex-Google guy who set it up, left. No one around who wants to put in the time to learn it. It seems like a general increase in complexity. It seems to replace the go mod stuff so we have something called gazelle that figured it out and third party ide plug-ins. The plug in for IntelliJ is janky. To top it all off, somehow we managed to get a build that is slow locally, slow on CI.

Well, it sucks that we’re at the “best practices” phase already

Meh back and forward don’t preserve location

In life, I can’t even manage to fail spectacularly. I get more of a like warm limbo of misery

Is this just tag bits in the reference pointer?

I stopped reading tfa after that terrible advice.

It only really works when the air is calm, so dawn and dusk.

I think put yourself in the shoes of someone about to be executed innocent of their crime. Then make your argument. It sounds like “some of you die, but it’s a sacrifice I’m willing to make” otherwise.

LEO WiFi, international space stations testing alfalfa growing in zero-g, “space walks” and moon returns. Meh. It’s the robotics probes like this one, Cassini, and Voyagers that are the exciting missions. Far bigger return for science.

If I have a 4K display, do I still need to worry about font rendering settings?

> Never heard of Qlot

> no notion of version dependencies exist (not even lockfiles exist

I think that’s the point of Qlot

Have iPhone XS Max, am I missing anything?

Installing it on my mid-2015 MBP thanks to Open Core Patcher!

When I was a kid learning pascal, I used beep() debugging (similar to printf debugging)

I'm getting performance measured based on number of tickets completed and number of PRs merged per quarter.

Does Rust have something like a reader macro where you can have arbitrary syntax for a bit?

Agreed. I always regret starting a new rails project with sqlite. Invariably I end up wanting some bunch of features only pg has.

Even for running tens of thousands of integration tests in a few seconds, pg is fine.

K8s is a Google thing for Google problems. It’s just not needed for most software delivery.

Edit: meanwhile I’m waiting 45 minutes on average for my most recent, single-line change, PR to roll out to k8s cluster at $massive_company that totally does this like everyone else.

We had to dump a Clojure code base for Golang because it was too slow for lambda usage. Does any of this release help with startup time?

Could this be fitted over the exhaust stack at coal and gas fired power stations for even greater efficiency?

> once saw an app that did bidirectional RPC over message queues

Haha I've seen this anti-pattern too (although I think it's in the enterprise patterns book??). It would bring production to a grinding halt every night. Another engineer and I stayed up all night and replaced it with simple REST API.

My belief too, as a grey beard 25 years in. I’ve seen all sorts of shit come and go.

There’s a lot of “slack” in the industry that we get away with. Ridiculous incidental complexity, far-out frameworks, architectural astronautics etc.

But if you care about “adding value” or your business succeeding, tools like Rails/Django are way to go. (And btw, use a RDBMS ffs)

Yes I remember that accident. I live and ride in that area. I wonder what happened.

This is great.

I personally have an image with Alexandria, Serapeum, Dexador, Bordeaux Threads, some JSON stuff, but it might be handy to have something others use as a similar target.

Probably stands a better chance of success than the over-pontificated CDR proposals, and CL21 which preceded it.

Curious if there’s a bunch of reader macros set up by default?

>> Convincing a whole generation of programmers that distributed lock are a feasible solution.

> I too hate this. Not just because the edge cases exist, but also because of the related property: it makes the system very hard to reason about.

I think this is a huge problem with the way we’re developing software now. Distributed systems are extremely difficult for a lot of reasons, yet it’s often or first choice when developing even small systems!

At $COMPANY we have hundreds of lambdas, DocumentDB (btw, that is hell in case you’re considering it) and other cloud storage and queuing components. On call and bugs basically are quests in finding some corner case race condition/timing problem, read after write assumption etc.

I’m ashamed to say, we have reads wrapped in retry loops everywhere.

The whole thing could have been a Rails app with a fraction of the team size and a massive increase in reliability and easier to reason about/better time delivering features.

You could say we’re doing it wrong, and you’d probably be partly right for sure, but I’ve done consulting for a decade at dozens of other places and it always seems like this.

> We should really standardize a core language for SQL

Do you mean something other than ISO/IEC 9075:2023 (the 9th edition of the SQL standard)?

Liked this bit:

> Like a cow shoved through the food manufacturing process and split into a million pieces

Fun to ride on with motorcycle