HackerTrans
TopNewTrendsCommentsPastAskShowJobs

62951413

225 karmajoined 6 lat temu

comments

62951413
·4 dni temu·discuss
Pro: In the last ten years backend development has turned into AWS SDK-orientied programming mostly. Databricks-oriented in case of data engineering recently too. Between this and python/js popularity it is more of unskilled labor now.

Contra: I'm reading digital circuits and introductory FPGA programming books this summer - fullstack development for the robotics dominated future here I come ;) Granted some EE classes in your old major will help. But modern digital circuits and embedded hardware space also have a lot of similarity to your muscle memory as a software developer.
62951413
·10 miesięcy temu·discuss
https://inside.java/2024/05/23/dop-v1-1-introduction/
62951413
·10 miesięcy temu·discuss
A typical Bay Area commute (e.g. to SJ or San Mateo/Redwood City) is 40+ miles one way. A typical weekend drive (e.g. to Half Moon Bay or Sonoma) is a 100-mile roundtrip.
62951413
·10 miesięcy temu·discuss
20 miles to SF, 25 yoe (backend, data, basic frontend), been there done that and all I have got is this automated rejection email
62951413
·11 miesięcy temu·discuss
Very few people want to re-create their production AWS MSK cluster from scratch. And that's the only way currently. MSK can usually upgrade Kafka brokers with minor performance degradation but not for this particular change.
62951413
·11 miesięcy temu·discuss
If you have a use-case where you currently allocate ~1K threads mostly waiting on I/O switching to virtual threads is a one-liner ("Thread.ofVirtual()" instead of "Thread.ofPlatform()"). No more golang envy for sure.

Depending on how much memory is used by the Thread stack (presumably 1M-512K by default, allegedly 128K with Alpine base images) that's your 1G-500M heap space usage improvement right off the bat.

The migration from JDK17 to JDK21 was uneventful in production. The only issue is limited monitoring as a thread dump will not show most virtual threads and the micrometer metrics will not even collect the total number of active virtual threads. It's supposed to work better in JDK24.

The Spring Framework directly supports virtual threads with "spring.threads.virtual.enabled=true" but I haven't tried it to comment.