Helge Heß

ultrathink, but in RL
https://github.com/helje5
#SwiftLang, #SwiftUI, #FOSS, #Cows, #NeXT, #Magdeburg

GitHub: https://github.com/helje5
Homepage: https://helgehess.eu
Business: https://zeezide.de

Public Key

npub1svetkp0j49gz064v9szutje235yxsscw4fexn5aahs6kzy7pwvfq5484dv

NIP-05 Address

helge_at_mastodon.social@momostr.pink

Profile Code

nprofile1qqsgxv4mqhe2j5p8a2kzcpw9ev4g6zrggv825unf6w7mcdtpz0qhxysprpmhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmntqyt8wumn8ghj7un9d3shjtnwdaehgu3wvfskueq3q53nu

Publishing to

relay.momostr.pink

relay.nostr.band

relay.primal.net

Author Public Key

npub1svetkp0j49gz064v9szutje235yxsscw4fexn5aahs6kzy7pwvfq5484dv

Show more details

Last Notes

2026-05-22 01:05:13 UTC

- reply

I'm just saying that push registration is already designed and implemented (for like 15+ years ;-)
You can probably find the relevant drafts somewhere in the Apple CalendarServer docs. It's not just for iCloud, it also worked for self hosted servers.

2026-05-21 19:44:27 UTC

- reply

CalDAV and CardDAV on Apple platforms do support push, did you look at that? You essentially need approval from Apple, but the protocol/mechanism is open IIRC. AFAIK FastMail is a third party that has the entitlement.

2026-05-11 21:25:27 UTC

People often complain about some SwiftUI bugs, lack of feature XYZ and such. But I think they often miss the structurally deep / conceptual issues. Like how many instance methods does `View` have? Something like 500+?
https://files.mastodon.social/media_attachments/files/116/558/041/517/108/576/original/2856f7abd7adcdd2.png

2026-05-06 00:03:49 UTC

- reply

Doch schon, aber der Sachverhalt scheint auch schon länger geklärt?

2026-01-12 20:07:20 UTC

- reply

Do we have numbers on that? My feeling is that they are actually quite similar, i.e. those who bought trashcans then bought Studios.

2026-01-10 23:26:49 UTC

- reply

That crap is produced in your country, not in the EU. Take your fights where they belong.

2025-11-04 02:15:58 UTC

Swift was introduced over 10 years ago. Promising better software quality due to the extensive static type checks, optional checking, etc over Objective-C.
Given the scope of the effort, surely the overall quality of the software in the Apple ecosystem should have improved significantly. Right? Yes, that's my impression as well 🏃‍♀️

2025-09-07 23:53:53 UTC

- reply

Isn't ISOFix rather easy?

2025-08-15 22:41:53 UTC

- reply

And this is any better on other platforms? 🤔

2025-07-06 01:21:29 UTC

- reply

I'm not entirely sure of the "why" though. In particular when you mention languages like Go or Rust which should be "memory" safe. Why wouldn't you just run the HTTP stack within a single process? Those langs are kinda guaranteed to be leak free? It is both more efficient but also more convenient. I.e. I don't see what you win w/ CGI.
This is different for C, C++, Swift and similar languages of course (a reason why I still think that mod_swift is actually a good idea).

2025-06-22 20:11:17 UTC

- reply

I wouldn't underestimate that. It isn't that different to "regular" users hacking up Excel macros or say Shortcut scripts (which usually s*** from a dev pov, but they do the job). It is an enabler, and as long as the users can properly rate the output, that is kinda ok (seniority again).

2025-06-22 19:46:43 UTC

- reply

I actually think it is mostly the same issue, just at a much, much lower speed. Someone who knows assembly usually writes better code (not because she is older, but has a solid understanding of how things work internally, though admittedly that may be counter today).
But AI brings that issue (not understanding what happens) from an acceptable level to 100x.
Either way, I think it can be helpful to senior devs because they can rate the output.

2025-06-22 19:25:05 UTC

- reply

If you get paid for that, sure 🙂 I still think AI is a huge issue because of the "stealing" part (doesn't matter what you call it, but I think we all understand the issue and that it leads to content not being published anymore publicly).
It's essentially the other side of the seniority coin, if everyone just synthesises code, there is no new input for number 5.
https://files.mastodon.social/media_attachments/files/114/728/648/399/950/338/original/4c3eb302c5fbc915.jpeg

2025-06-22 16:53:44 UTC

- reply

Do they discuss how people are going to acquire those 10% in the future (I assume those are the advanced seniority 10 percents?)

2025-06-17 14:21:49 UTC

This inspired me to build proper JavaScript operators for #SwiftLang: https://mastodon.social/@BrendanThompson/114697574788565486
No more inconsistency w/ the language of the web! Gist: https://gist.github.com/helje5/4da7f58649ebeb842b9acd7215fae1c4
https://files.mastodon.social/media_attachments/files/114/699/145/485/995/237/original/b47cb7ed6cb4dbf6.png

2025-05-10 23:09:04 UTC

It is *very* tempting (and easy to fall back to) but my recommendation for #SwiftLang concurrency is the same I have for #SwiftUI. Do NOT try to map your existing knowledge to the new system. An actor is not a GCD serial queue, just as a SwiftUI View is not the same as a UIView.
You essentially have to learn both from scratch, prior knowledge is more of a distraction leading to wrong paths of thinking about them.
Those things solve similar problems, but are very different things.

2025-03-20 00:30:51 UTC

- reply

FWIW I don’t think it says that attached DBs disable WAL or multiple readers, just that the transactions are local to the respective databases?

2025-03-20 00:04:49 UTC

- reply

read the docs 🙈

2024-12-19 02:48:58 UTC

- reply

That’s probably true for VR, but AR kinda doesn’t make sense at all when it is tethered to a desktop.
Either way a display only version would have been a good choice for dev.

2024-11-15 23:22:17 UTC

- reply

Fitting to a platform that doesn't even have a C ABI?

2024-10-29 00:58:56 UTC

- reply

It does? It specifically states that this issue only exists when using the same connection in different threads. It describes the limitation for that particular (and unusual) setup.

2024-10-29 00:54:42 UTC

- reply

It's not about exactly this problem. Your issue is a difference in your Go database driver behaviours, which you should report if you care. It's a Go API issue.
The SQLite documentation specifically states this because SQLite, unlike most other databases, can actually reuse a connection from multiple threads. Which doesn't mean you _should_ do this, to the contrary.

2024-10-28 23:59:25 UTC

- reply

I don't use Go and won't do any experiments. I recommend you just file a bug w/ the SQLite driver for Go if you want to get the issue fixed. It's not a SQLite issue but a Go driver one.

2024-10-28 23:03:56 UTC

- reply

The implementation obviously does matter 🙂 I suspect the db.connect in the MySQL driver doesn't give you an actual connection but a proxy that will open a connection when necessary (i.e. is a pool). While the SQLite one gives you an actual connection, which you then can't share between threads.
So yes, that seems like an unfortunate difference in the implementation of the two drivers in your environment. Not great. (i.e. you should file a bug w/ the Go SQLite driver)

2024-10-28 22:57:10 UTC

- reply

If you run it from multiple threads, yes. I would assume the exact same is true for MySQL.
But maybe your `db1 = db.connect('user:pass@database')` is not actually giving you a connection but rather a pool, and then the prepare will open the actual connection? What client library/environment do you use?

2024-10-28 22:50:09 UTC

- reply

Just use different connections for different threads, exactly the same way you do it w/ MySQL. Then everything will be fine, the issue is exclusively if you use a single *connection* from multiple threads. Which unlike in regular DB's is actually possible in SQLite (if SQLite is compiled w/ the right flags). But still not advisable.
By "handle" you mean a prepared statement? Yeah, the last-id is bound to the connection, not to a statement.

2024-10-28 22:38:30 UTC

- reply

Why would you use two threads with a single connection? That wouldn’t work well with MySQL either (probably wouldn’t work reliably at all)

2024-08-21 20:20:32 UTC

In many ways Apple almost seem to be a storage company now. It sells a tiny slice of slow online storage, 50GB, for $1 a month. Or 250GB extra on your Mac for like $200 🙈
(the hint that I have to educate my "family members" to produce less digital junk also feels borderline offensive)
https://files.mastodon.social/media_attachments/files/113/001/850/644/169/209/original/47de379bfc5eb1ff.png

2024-08-17 00:00:38 UTC

- reply

Interesting. Over here almost all cooking is electric since forever (I had a gas field when I was living in CA), and well induction is much better than plain coils.
It’s a little hard to compare to gas, it is quite different, but I feel it is much more practical (easier to clean, no smells, very precise, etc)

2024-08-16 23:51:57 UTC

- reply

It’s a little bit like with electric cars, even the very cheap ones are technically more advanced, more efficient and just cheaper, ie generally better.
I also enjoy gas based cooking on my grill, but a good induction field is like $800 and i’m not sure why I would want anything else inside.