Does it mean it can run Java compiled to Native Image?
Why not full VM with JIT? Seems much easier and more compatible with apps out there.
Readit NewsDmitryOlshansky commented on Introduction to Unikernel: Building, deploying lightweight, secure applications tallysolutions.com/techno... · Posted by u/eyberg
DmitryOlshansky commented on Cucumber lets you write automated tests in plain language cucumber.io/... · Posted by u/nateb2022
Used cucumber as living specification for our search engine. Sooner or later we realized it was just matching a list of expected JSONs with a bunch of awkward Given, And Then mixed in. Scraped that stuff for our own Kotlin DSL, made the whole thing more flexible and faster to boot.
DmitryOlshansky commented on What went wrong for Yahoo dfarq.homeip.net/what-wen... · Posted by u/giuliomagnifico
I recall the Zookeeper paper from Yahoo scientist which basically details a more useful version of Google’s chubby. I find reliability and design of Zookeeper fascinating these days cool kids use etcd mostly because of relatively complex protocol of Zookeeper (there is a few implementations but they lack the polish of Java client).
Null modem LAN parties!
I recall playing Warcraft I with my friend over null modem. Kind of boutique LAN party.
DmitryOlshansky commented on RFC: PHP license update wiki.php.net/rfc/php_lice... · Posted by u/josephwegner
I honestly can't think up a reasonable case for a triple "naked" pointer. Nevermind performance, it's a level of implicit indirection that you simply can't reason about.
Think of what a pointer is. Picture a struct; accessing a member is dereference + offset. It makes sense, you know there's a car, and the car has a steering wheel, and the steering wheel has a horn button. Simple. A struct with one field, that field has an offset of zero - it fits our "naked pointer" case 1:1, but is more readable. The compiler will do the rest.
As my dear friend often noted, "why simple?"
Think of page tables this is essentially a table of tables of tables. I also was meh on triple pointers until I found this use case.
DmitryOlshansky commented on C3 solved memory lifetimes with scopes c3-lang.org/blog/forget-b... · Posted by u/lerno
Wow, this is such a fascinating concept. The syntax can’t stop reminding me of @autoreleasepool from ObjC. I’ll definitely try this out on a small project soon.
Also, since D lang usually implements all kinds of possible concepts and mechanism from other languages, I would love to see those being implemented aswell! D already has a borrow checker no so why not also add this, would be very cool to play with it!
I think there was a discussion to add SuperStack a threadlocal buffer that will be used for arena style allocation back in 2010-2011. While std wont have it I see no problem implementing one yourself.
DmitryOlshansky commented on Can an email go 500 miles in 2025? flak.tedunangst.com/post/... · Posted by u/zdw
We have a program which the company who developed lost the ability to rebuild the app for some reason.
It has a 500ms timeout to load some settings from a server in the UK via TLS. If it goes more than that 500ms (or something, it's unclear the exact timeout cause) the app just vapourises.
This is fine in the UK, TLS needs about* 3 times RTT to complete though, so an RTT above about 160ms and it's screwed.
Almost all our users are in the UK, europe, mid-east or east coast USA, and in that 160ms RTT range.
We ran into issues when a dozen people tried to use it in Australia, so the principal still happens with some badly written code.
Patching the binary is an option, though it’s tricky I would attempt it anyway.
Not actually that hard with a redis lock or any database (Postgres has a specific lock for this but you could also just use a record in a table)
Far easier than the original single threaded solution - and has fault tolerance baked in cause you can run it on multiple clients
Or zookeeper for that matter.
DmitryOlshansky commented on Event – Fast, In-Process Event Dispatcher github.com/kelindar/event... · Posted by u/kelindar
> Generic: Works with any type implementing the Event interface.
Isn’t this the opposite? Generic is usually implying any type would do.
A drop-in memcached replacement written in D. The end goal is Redis but memcached is simpler protocol (and less data structures;)) to test the waters.