chrnola

Guaranteeing order has its tradeoffs.

There is work happening currently to make Kafka behave more like a queue: https://cwiki.apache.org/confluence/display/KAFKA/KIP-932%3A...

Miss you all dearly.

This book[1] was a great read on the topic.

[1]: https://ethanmarcotte.com/books/you-deserve-a-tech-union/

Same. I would rather put up with being burnt out than subject myself to interviewing. Ridiculous.

ManicTime was a lifesaver when I was working as a consultant and had to attribute every hour of my week to one of several clients.

Sometimes, but the differences in performance between the two were quite vast if I recall correctly.

Oh interesting. Might explain why Apple employees aren’t feeling this same pressure. Do you know if Apple’s MDM is the same for their retail and corporate employees?

Also - I’m not super well versed in MDMs, but they seem to come in two general flavors/deployment strategies: bring-your-own-device (BYOD) and manage a fleet of employer-owned hardware.

In my experience, I’ve only ever seen BYOD policies for employee-owned _smartphones_ (e.g. for access to an intranet mail server). I’ve never worked anywhere that permitted employees to use their own _workstations_.

For the record, I did not return my (4x cheaper) iPad. I didn’t ever buy a Vision Pro. Because of the Apple ID issue. I’m trying to convince Apple that they should care because they lost a sale.

This is an incredible point that I had not considered.

Employers could be free to restrict use of such devices via MDM policy if they wanted.

Also, how many of us have purchased keyboards, mice, displays, headphones, etc with our own money that we happily use with employer owned computers because it’s safe to do so?

Consider the setup process for the Apple TV. The TV shows a unique one-time-use QR code-like pattern that you can scan with the camera of an iOS device. Surely something like this would be sufficient for pairing a Vision Pro with a Mac.

Also the security implications of encouraging people to add their personal Apple ID to devices they don’t own are, IMO, worse.

> I bet Apple’s own employee issued macs are managed

I thought so too. The Apple retail employee that gave me the demo of the Vision Pro confirmed this. He said the manager at his store had a Vision Pro and wanted to use it with his Apple-issued Mac, which was managed via MDM.

underrated comment

Hmmm I thought it ran its own web server instead.

There’s some special handling for FETCH_HEAD too (i.e. which branch on a remote is considered the default).

Maybe I’m just hopelessly cynical, but I suspect that this is representative of the average developer’s experience.

Also it’s (indirectly) an ad for a product that they’re selling to help devs achieve this.

That’s quite the assumption! You’d also have to know that your shell maintains a history and know how to search it. None of these things are obvious to those who do not already know them. We all had to learn at some point.

As the parent comment says, the specifics of the example are irrelevant. Pretend you didn’t know that the dictionary file existed, or where it was stored, or that cat/shuf/head existed, or even how to compose programs in your shell.

What kind of response would be appropriate then for getting them to take this issue seriously?

This bit is no longer entirely accurate:

> For highly proficient users, this gets even worse as their is no command key equivalents for cut, copy, or paste. […] Part of the unspoken reason desktop clipboard use is so high is the speed in which it can be used. Mobile has none of this.

I recently discovered [1] that iOS has several three-finger pinch/swipe gestures for copy, paste, cut, undo, and redo. Apparently these gestures were introduced in 2019/iOS 13 [2]. While they are certainly not the easiest gestures to reliably perform, they at least do not suffer from the issues of ambiguity described by the author.

[1]: accidentally, of course, because the discoverability of many features on mobile is quite poor

[2]: https://9to5mac.com/2019/06/12/gestures-undo-ios-iphone-ipad...

Yeah agreed, especially now that PowerShell is available cross-platform.

Nushell[1] also seems like a promising alternative, but I haven’t had a chance to play with it yet.

[1]: https://www.nushell.sh/

The linked article literally mentions qpdf within the first few paragraphs.

I would amend this just to “delivers value”.

I’m having a hard time understanding this line:

“Developers cannot take advantage of the full power of the underlying database for fear that the complex, opaque nature of SQL query behavior will overwhelm their ability to understand how queries perform, and quickly address problems when they do come up.”

What does that mean? Developers are somehow sacrificing database performance (“full power”) because they’re too scared to write SQL?

Correct. No jailbreak required!

The caveat for enabling JIT support is you have to “attach a debugger” first. AltServer automates this process…provided your iOS device can communicate with it when launching the app.

If you’re using the Arc browser, try out this Boost: https://arc.net/boost/E4A26AD9-F0FF-4247-AEAE-27D071FB546B

I was kicking around a similar idea a few months ago but for a single-user Mastodon instance. Obviously a phone is a huge single point of failure, but there are likely dozens of hobbyist use-cases like this that don’t need strong reliability guarantees.

That’s an interesting idea! Reminds me of how Pyroscope’s continuous profiling data can be linked to OpenTelemetry traces[1].

[1]: https://pyroscope.io/docs/java-tracing/

Link appears to be dead now.