People think they can do it themself... kind of like how everyone build their own database using Microsoft Access in the 90's. When all software developers needed to repair all the issues...
1,064 karma · joined June 24, 2017
Socials: - github.com/ivolimmen - codeberg.org/ivolimmen - reddit.com/user/ivolimmen - deezer.com/us/profile/6410927063
Interests: Open Source, Privacy, Programming, Remote Work, Technology, Web Development
---
People think they can do it themself... kind of like how everyone build their own database using Microsoft Access in the 90's. When all software developers needed to repair all the issues...
We quickly replaced part by part by easier, less costly parts.
Software development is not just writing code; I think all HN users know that.
Humm that's like 2 or 3 countries?
Who (not including geeks) would want to go faster than 1Gbit?
If we want to compress a file we normally just wrap the file ouputstream in a GZIPOutputStream so we add features by wrapping it.
Yes Java does not have an alternative for Linq and jooq is a poor knock-off compared to this but then again: I do not care much for JPA/Hibernate.
-Java always has an API, .NET is about extending an existing application (Servlet API vs IIS)
-Java has a nicer IO as .NET has bidirectional streams (You can't wrap streams in .NET).
-Linq is nice but has a huge caveat: if a Linq provider does not implement it fully to falls back to the .NET collections. So trying to 'Skip' and 'Take' on a ActiveDirectory will fall back to collections in memory and cause a crash on a huge AD in production (Yes had the pleasure).
-Java's Eco-system is way bigger.