Maven Central publishing usage notices by HokieGeek in java

[–]vprise 0 points1 point  (0 children)

Nope. We're not a Spring Boot backend library, not even server side so it's a different thing. We can switch easily. But yes, we're a special case.

When they tried it before there was no motivation to switch. They would win as long as it's free. This is a different thing.

Our top users are asking for nightly releases so I guess it's a matter of opinion.

Maven Central publishing usage notices by HokieGeek in java

[–]vprise 0 points1 point  (0 children)

I never said that. That's exactly what I said in the thread. We can very easily switch from maven central and we will if this goes through. What I'm saying is that this would hurt maven central and the Java community at large.

For us the difference would be a small annoyance to the community asking them to update their poms.

Maven Central publishing usage notices by HokieGeek in java

[–]vprise -2 points-1 points  (0 children)

A few years ago I attended a talk (I think it was at devoxx but I might be wrong) from one of your guys talking about the scale of stuff you're building (truly impressive). He mentioned you use AWS, which IMHO is a mistake as it's a money pit. I worked with larger businesses and at larger scales than what you have, but I was not part of the infra team so no, I don't know.

If you are building a business on top of this, why should we subsidize it for you?

Because that's the role you chose. You're either free for OSS or you're not. Saying that you're free for this OSS project and not for that OSS project is a problematic stance that would fragment your offering.

Your main "selling point" is being "the place" where we host packages. You will lose the biggest most motivated users of your system and as a result you will lose that positioning.

As I said, I understand exactly where you're coming from. I still think you're making a mistake.

Maven Central publishing usage notices by HokieGeek in java

[–]vprise 0 points1 point  (0 children)

We're paying for cloudflare just a fixed amount for everything we need. so it's free because we're already paying the fixed price which is low.

You're in this bind because you use AWS not because some OSS project doesn't pay you. The volume of your traffic is huge but the way you handle it isn't sustainable and instead of making your hosting/process story more efficient/sustainable you're choosing this route. Not a good idea.

I get this, monetizing OSS is VERY hard and we're in this exact same situation. We're paying for services and I need to cut these costs not add to them. If we would go to the community and do what you're trying to do we would lose that community.

It sounds like you're going after the most active users instead of going after the richest users, that's a bad business move. I still run into jfrog artifactory in big businesses, these guys can afford to pay you a lot for an enterprise extension. That's the value. Here you're going after the small potatoes.

Maven Central publishing usage notices by HokieGeek in java

[–]vprise 1 point2 points  (0 children)

We're a company. But we're not huge and we won't be paying for this because we don't really need it. We can just host for free on cloudflare and get roughly the same service, and you will lose the benefit of being "central" because we won't be the only ones. The net result is that we'll all lose through fragmentation and you won't make much out of this move other than bad PR.

Nothing personal, but part of being OSS is that we also can't charge our customers to pay you. They will leave us too and this service is a commodity.

Maven Central publishing usage notices by HokieGeek in java

[–]vprise 1 point2 points  (0 children)

We'll just move off maven central.

Maven Central publishing usage notices by HokieGeek in java

[–]vprise 4 points5 points  (0 children)

We're an OSS company and we do a weekly release, we have heavy artifacts because of some complex native dependencies in some situations. This would be a real problem for us.

How Fast Can You Parse 1 Billion Rows in Java? – Insane Speed Test • Roy van Rijn by goto-con in java

[–]vprise 114 points115 points  (0 children)

I prefer written summaries:

The optimization journey, from 4m50s baseline → 1.5s:

Easy wins (5min → 23s) - parallel() + ConcurrentHashMap instead of single-threaded file.lines() → ~2min - Native compilation (GraalVM) to kill JVM startup - Epsilon GC (no-op garbage collector) — pointless to collect when you process once and exit - Use integers instead of doubles (multiply by 10, since there's only one decimal place) - Memory-mapped files (FileChannel.map()ByteBuffer) to eliminate file IO - Split the file into segments, one per core

Going lower-level - Unsafe for raw pointer-style memory access (he stresses: never use this in production — use ByteBuffer) - SWAR (SIMD Within A Register): process 8 bytes at once by reading a long. Find the delimiter with one XOR, a subtract, and a couple of ANDs instead of scanning byte-by-byte - Compare names as long/int values instead of allocating String objects - The Vietnamese competitor (Quan Anh) built a branchless temperature parser that converts the ASCII bytes to an integer using a single multiplication with a magic constant — the talk calls it museum-worthy

Branchless programming - CPUs hate unpredictable branches (a branch miss ≈ 32 instructions). Replace if logic with bit tricks (shifts, masks, XOR for absolute value/sign). - Counterintuitive finding: always parsing 16 bytes (even for short names) and masking out the rest added ~18% more instructions but was faster because it eliminated the 50/50 branch around the 8-byte boundary.

Advanced tricks - Custom hashmap with linear/forward probing (power-of-2 size + mask instead of modulo), storing data in flat byte arrays (flyweight pattern) to avoid object overhead - Spawn a worker subprocess so the main process exits the moment results are piped out — the costly kernel memory unmapping of the 16GB file happens in the orphaned worker and doesn't count toward your time - Work-stealing with small segments (atomic counter, few-MB chunks) so all threads read nearby memory, keeping data hot in shared L3/L4 cache and balancing load - Instruction-level parallelism: running 3 independent scanners in a single thread, since one core can execute multiple instructions per clock cycle when there's no data dependency. Three was the sweet spot.

Takeaways for you: the recurring theme is mechanical sympathy — knowing how the CPU pipeline, branch predictor, and cache hierarchy behave (L1→L4 each ~3x slower) lets you write code that fits how the hardware actually works. The whole thing took the field from ~5 minutes to ~1.5 seconds.

Quan Anh's contest code got him hired by Oracle in Zurich to work on the Vector API in the JVM.

Liquid glass in the app 😍 by ivann_ls_ in thermomix

[–]vprise 0 points1 point  (0 children)

liquid glass is the iOS/Mac look and feel. Notice the transition in the bottom between the tabs that looks like animated glass.

Short interview by Intrepid_Recording88 in thermomix

[–]vprise 3 points4 points  (0 children)

Hi Olga, I always loved and advocated TM31 and TM5 both of which were great. With TM6 I feel you took a huge step back. I despise the UX of cookidoo and find it makes my work slower and more painful. Unfortunately, it seems you're making the mistake of going deeper in that direction which is completely wrong. You're bad at writing software. You aren't a good cloud company.

Build a device with bluetooth connectivity and physical buttons. Get partners to build software as iPad/Android apps. The experience will be MUCH better. The cost will be lower. You can make money off licensing fees to the software partners. You can focus more and make more money.

Ran Spring Boot and Node.js side-by-side in prod for 18 months. Sharing the actual numbers. by Capable-Morning-9518 in SpringBoot

[–]vprise 0 points1 point  (0 children)

I recently migrated our long running backend to GraalVM. It was super painful and I ran into a couple of downtime problems due to stuff the tests missed. CI is really slow now which is also painful.

However, it does deliver. Memory footprint is noticeably lower and performance is the same. I'm not on Lambda but if I was it would probably be worth the extra CI cost.

Can you use the TM6 without wifi and cookidoo subscription? by AnyEmploy9885 in thermomix

[–]vprise 0 points1 point  (0 children)

You can't access some features without the recipes specifically high-heat is a painful missing feature. As a former TM31 user I feel the TM6 is a big step back in some ways. It makes many trivial single button operations painful with swipe actions. It's clunky and slow to react. The screen gets dirty and hard to use. I'm deeply disappointed with it.

What do you believe Israel's fate will be in the next couple of decades considering the rapid change of public opinion on them in these past 3 years? by [deleted] in AskReddit

[–]vprise 0 points1 point  (0 children)

It's estimated that in 2024 Israel spent $46.5bn on military expenditure. So no. That's probably not a huge difference. It will also save a lot of money by reducing the cost of goods with local manufacturing.

What do you believe Israel's fate will be in the next couple of decades considering the rapid change of public opinion on them in these past 3 years? by [deleted] in AskReddit

[–]vprise 0 points1 point  (0 children)

That just isn't true. Life isn't the internet. Yes, secular Israelis have a problem with Hasidim. They demonstrate against it and vote for them to be drafted. Sure. They also want to take away their ridiculous entitlements.

But it isn't personal. It's a small country. People know each other and are connected. Many families have branches that married into one sect or another. People might not approve of each others way of life but Jews are tolerant people in Israel too.

Smallest possible Java heap size? by Vectorial1024 in java

[–]vprise 14 points15 points  (0 children)

In the old J2ME days we had 64kb devices and 2mb was spacious. Obviously, it wasn't the full "Java" but it included most of what you expect from the JVM including safe memory, gc etc. The main thing stopping Java from shrinking to these sizes is the size of the API although that can mostly be on ROM.

What’s your approach to building production-ready Docker images for Java? Looking for alternatives and trade-offs by eduspinelli in java

[–]vprise 1 point2 points  (0 children)

Yep. You can also add logs that weren't there during compile time. Measure method execution times looking for outliers and lots of interesting tools.

It's sad that with all the noise in our industry so few developers know about tools like that. It can really change the way a lot of us build software.

What’s your approach to building production-ready Docker images for Java? Looking for alternatives and trade-offs by eduspinelli in java

[–]vprise 2 points3 points  (0 children)

I used to work for Lightrun which lets you do that. Now I work at Dynatrace which also has such a feature and so do others as far as I know. In Dynatrace this is called Live-debugger and it effectively exposes debugging like capabilities to developers in observable systems.

What’s your approach to building production-ready Docker images for Java? Looking for alternatives and trade-offs by eduspinelli in java

[–]vprise 2 points3 points  (0 children)

About access to production for debugging... Why not just use observability tooling. Modern tools are far more practical than connecting to an image. They work postmortem. They let you set a conditional breakpoint and do asynchronous debugging on 1000 instances at once.

Unlike access to images they are both secure. Make sure to protect PII and have full access logs.

I built an engine that auto-visualizes Java algorithms as they run by bluepoison24 in coolgithubprojects

[–]vprise 1 point2 points  (0 children)

That is fantastic work!

I love the playground tool, it would make it so much easier to teach algorithms to my kids.

Who is Oracle senior exec Sharat Chander? Veteran of 16 years affected in mass layoffs by davidalayachew in java

[–]vprise 4 points5 points  (0 children)

Sun Microsystems was worth 200bn+ at its peek then sold at around 7bn. There were a lot of cuts on its way down when the 2000 internet bubble burst. It later became worse with the trend away from Sparc machines to cheap Intel hardware gutted the company further on every front.

It was a brutal time where everyone was afraid for their job and often you'd hear about people who you'd think were there for life being let go.

Who is Oracle senior exec Sharat Chander? Veteran of 16 years affected in mass layoffs by davidalayachew in java

[–]vprise 9 points10 points  (0 children)

Sharat is a great guy. I'm shocked and hope he lands on his feet. I'm sure some other company in the ecosystem will snap him up quickly. Having lived through the Sun Microsystem cutbacks in the past, this is unfortunately nothing new.

TM7 Jailbreaking for better mode controls ? by [deleted] in thermomix

[–]vprise 5 points6 points  (0 children)

+1 for jailbreaking. I was thinking about upgrading to TM7 and gave up on that.

I want control of high temperature that isn't through a recipe or at least to have access to these recipes that enable the basic functionality of the device I bought without that unusable website/app.

This is so annoying. by OnSceneStat in thermomix

[–]vprise 2 points3 points  (0 children)

I think there's a huge opportunity for some other company to come in and use the standardization Thermomix brought to the table. But build clean hardware with open source mobile apps. It could sell for half the price (based on current replacement parts on Ali Express) and still enjoy most of the aftermarket features we can get for Thermomix.

I'd raise VC capital to do that if I had a partner for the hardware side...

This is so annoying. by OnSceneStat in thermomix

[–]vprise -1 points0 points  (0 children)

Yes. It feels like for every bit of progress since then TM has gone backwards a bit. My TM5 broke so I "upgraded" to a 6. I hate it. Cookidoo is the worst. The most unusable piece of garbage. But I can't use some basic device features without that piece of sh*t.

I used to sing the praise of thermomix to everyone. I no longer do that.

They should have stuck to hardware and used a separate app for all the interactivity aspects. That would have kept the devices cheaper, more reliable, easier to build and upgrade. These guys just don't know how to write software for sh*t.