9 ms·
I think this is a story that gets repeated lots of times in our world of open source software dev. 1. X is SO bloated and poorly engineered full of bad legacy
by jrochkind1 8y ago
I think this is a story that gets repeated lots of times in our world of open source software dev.
1. X is SO bloated and poorly engineered full of bad legacy decisions.
2. We can totally do better let's invent a new thing, Y!
3. Wow, Y is so clean and fast and understandable.
4. But it doesn't do this thing a bunch of people reasonably really need... let's add it.
(repeat 3 and 4 a few hundred times)
5. Y is so bloated and poorly engineered and full of legacy decisions. We can do better! (Go to 1.)
The grass is always greener, but mature complicated software is _usually_ complicated for... reasons.
- manigandham 8y agoYes, because the loop never solves the original problem. It's about organization and bloat, not pure speed and leanness. Rebuild from scratch but also recreate all the existing functionality in a much better standard library and finally the chain can be broken. But nobody wants to do that.
- ahansen 8y agoI believe this is what Microsoft is trying to do with .NET Core. It's been successful so far, though they aren't at feature parity yet.
- manigandham 8y agoYes, arguably the .NET Framework almost did it and is still one of the most productive frameworks available, but .NET Core has definitely improved things substantially. It's fast, well-designed, and full-featured and I expect usage to pick up greatly.
- lewisinc 8y agoCan I use F# with it? Because I would love to learn me some F# some day.
- manigandham 8y agoF# with .NET Core? Yes, it works fine. There are some challenges coming up with design changes to the compiler and C# that might overlap what F# already has but it'll get sorted out.
- vizzier 8y ago.net core F# support has been pretty great from the initial stages of .net core from my basic usage. Biggest challenge seemed to be around type providers (F# system of generating strongly typed classes from dynamic data such as XML, CSVs, HTTP etc) but that's largely resolved. More info at https://github.com/fsprojects/FSharp.TypeProviders.SDK https://github.com/fsprojects/FSharp.TypeProviders.SDK Great resources for getting started with F# at https://fsharp.org/ https://fsharp.org/ My personal preference is generally to install the SDK and use the http://ionide.io/ http://ionide.io/ with VScode as it seems to work most reliably cross platform.
- davidgrenier 8y agoI'd be very much interested how anyone is using F# on Linux without mono. I have .NET Core but the whole thing seems to require Mono and it isn't clear from fsharp.org that you can do without.
- workinthehead 8y agoMono is not required: https://docs.microsoft.com/en-us/dotnet/fsharp/get-started/get-started-command-line https://docs.microsoft.com/en-us/dotnet/fsharp/get-started/g...
- zzbzq 8y agoSo far the package manager hell has been kept in check because they keep re-doing everything in such a way that you don't intermingle it. So when you're on MVC5 you're on MVC5, and when you're on AspNetCore, you're on that. You're not using 5 of library x and 6 of libarary Y. Likewise the startup and DI stuff has all fully rebooted twice in a few years. But nonetheless, some of that sort of package hell has already seeped in, where you're using different packages that depend on different versions of some underlying thing with breaking changes. I think the choices are either keep rebooting everything or stop making new stuff.
- manigandham 8y agoYes, but it's rapidly getting better with .NET Standard combining all the libraries into a single definition that can be used on any framework implementation. MVC5 was never released though, and the changes have been rather minimal from ASP.NET Core v1 to v2 with straightforward migration guides, so it might look messier than it actually is if you were working through all the previews and release candidates instead. Nevertheless, Microsoft has a long history of having messy v1.0 with most of the stability coming after v2.0, so you can consider the foundation pretty stable now that it's on v2.1 and more.
- poilcn 8y agoWhat I don't like in Microsoft's frameworks is that they've made lots of things multiple times in slightly different variations, like they always do with all their software (10 variations of each type of programs which were outdated before they were finished). Mostly it exists due to historical reasons, but it only underlines the problem of a multi-billion corporation having design skills of a sophomore. They redo and redo things, bloating their frameworks and increasing their number and you have to guess which CookieContainer you should use this time. It makes me understand why language designers like Rust developers insist on a small core library. Because it's better to have one separate library that will do everything regarding Cookie management (and you could control its functionality by including additional traits from it), than to have incompatible variations of it in the standard library and in each framework.
- pjmlp 8y agoAndroid Frameworks will make you love .NET variations.
- rubber_duck 8y agoC# is very verbose and tedious compared to more expressive languages - having to deal with CLR types/API at runtime while using a language with very limited expressiveness (C#) is not very productive. It's better than Java if that's what you're aiming at - but JVM has an incredible ecosystem of stuff that works - much larger than .NET core which is not very mature in many areas (recently had to revert to .NET 4.7 because some encryption method used by a government SOAP service we were talking to wasn't supported). TypeScript and JS underneath is actually quite malleable - you can escape static typing at any point and revert to simple JS object model when things don't map cleanly in the type system - and then still have types at the boundaries - makes meta-programming trivial in some cases - where it would look like a monstrosity in C#. F# is interesting and has a lot of advantages over C#, but few people seem to be willing to invest the time to pick it up in the .NET community. So I don't really view .NET core as a superior alternative, I've worked in JVM land, they are more mature and while Java sucks there are other languages on top of it as well and are decent to use (Kotlin ~ C#, Scala ~ F#)
- Quarrelsome 8y ago> using a language with _very_ limited expressiveness (C#) is not very productive. o_0. Think you need to check yourself mate. I believe the productiveness of more "expressive" language tends to be undermined by the loss of productivity that occurs when you're compelled to write blog posts or comment on hacker news about how amazingly productive and expressive your language is.
- btschaegg 8y ago...as if we wouldn't be writing comments on HN anyway. ;-)
- rubber_duck 8y agoI can do like 3-4 hours of productive work a day realistically - after that I lose focus. I can push this in some periods - but that's the ammount of time I limit myself to be functional over long term. If I need to waste that time sifting trough boilerplate than I'm pretty upset because I get less shit done in that time window. Chatting on forums is a casual brain teaser and keeping up to date on industry stuff.
- pspeter3 8y agoI think Go does this for me for the most part
- hshehehjdjdjd 8y agoGo has been out for almost a decade and they’re still working on the package management story.
- nojvek 8y agoI’m super bullish on rust. I feel like it was designed with the right intentions.
- algesten 8y agoI love rust, but the standard libraries are nowhere near the same abstraction level of nodejs. All services I've deployed built on rust pulls in a kitchen sink of deps. Granted. I get a static binary as my end result, so maybe it's fine.
- jzoch 8y agoRust is designed that way, to be fair. They expressly did not want to be batteries included like python is. The reasons are what they are and not particularly relevant to the conversation, but pulling in well designed third party crates is the point.
- devxpy 8y agoSpeaking from a python user's perspective, the batteries included philosophy works great when you have a neutral implementation. Python does a good enough job, and provides extensibility in a way that I don't need to download a package to do basic things. On the other I have to spend hours trying to find a package in JS that just gets shit done. The third party package way is only required for ui parts because you don't want everything to look generic. But having a good standard library to do non user facing stuff is essential. That's why every node project ends up with a thousand dependencies. Because the language is not batteries included. There in JS there is no "one correct and obvious way to do everything" which makes doing basic programming painful.
- BigJono 8y agoNot everything that gets added is stuff that people reasonably need, either. If you cater to everyone's needs, then you'll end up with 10 solutions for the same problem, because every one of your users has their preferred one. I think Javascript suffers from this quite a bit. ES6 "classes" should never have made it in, for example. Not only did they add an extra level of abstraction for beginners to learn, but the only reason for doing so was "my code doesn't look like it does in other languages"...
- mieseratte 8y ago> but the only reason for doing so was "my code doesn't look like it does in other languages"... As much as I beat the FP drum these days at work, I find the class syntax a much nicer way of organizing solutions to certain, pardon the pun, classes of problems. Whether or not you find this to be semantic diabetes is a matter of taste, I suppose. I'm curious what, specifically, you find to be the major issue that makes you say they should have been left out.
- nojvek 8y agoES6 classes were such a relief compared to the prototype bloat you had to right. I love syntactic sugar that makes my life easier. ES6+ flavors of JS & Typescript really made me take web programming seriously again.
- noir_lord 8y agoAgreed, classes with typescript and Vue make sense to me in a SFC approach. Something about components just fits the class model well.
- wow-bot 8y agoalso agree, would not go back. TypeScript is savage
- elyobo 8y agoI loved the classes at first, but as I've got more in to it I've found that classes and prototypes are redundant. Closures let me maintain all of the state that I need without the extra boilerplate.
- edgartaor 8y agoObligatory xkcd reference: https://xkcd.com/927/ https://xkcd.com/927/
- redavni 8y agoThis is why it's so important to have good leadership. For example, Linus Torvalds.
- pknopf 8y agoHow do you break the loop?
- stcredzero 8y agoRefactor and trim the bloat on the basic libraries, but have a policy where bulletproof automated source rewriting tools are provided in those cases. Perhaps this isn't possible with Javascript, but it might be possible with other languages.
- pc86 8y agoIf you think anyone has "bulletproof automated source rewriting tools" I've got a bridge to sell you.
- stcredzero 8y agoIf you think anyone has "bulletproof automated source rewriting tools" I've got a bridge to sell you. I've used an excellent one. The Refactoring Browser parser engine in Smalltalk. I've used it to eliminate 2500 of 5000 lambdas used in an in-house ORM with zero errors -- all in a single change request. (Programmers were putting business logic into those lambdas.) Like any power tool, it's not stupid proof. However, it gives you the full syntactic descriptive power of the language. So if you can distinguish a code rewrite with 100% confidence according to syntactic rules, then you can automate that rewrite with 100% confidence. Here's where it can go wrong: If your language is too large and complicated, there the probability you can run into a corner case that will trip you up. Also, it will always be possible for a given codebase to create something which is too hard to distinguish, even at runtime. (You can embed arbitrary code in a Refactoring Browser Rewrite transformation, so you can even make runtime determinations.) "Bulletproof" isn't "invulnerable." A vest with an AR500 plate will stop certain bullets hitting you in certain places. It won't protect you from being stabbed in the eye or stepping on a landmine. Despite that, it is still a useful tool.
- jrochkind1 8y agoWhat's the bridge, how much, and is what everyone else is using and/or the next big thing?
- stcredzero 8y agoExactly! "originally X was presented as a bloat-free alternative to 'enterprise languages'" For awhile, "Burn the Diskpacks!" was a battle cry of the Squeak Smalltalk community. That sort of policy fights bloat, but leaves old users in the lurch. I think that we are now to the point where a language/environment can trim bloat while not abandoning old users. If the language has enough annotation, and has the infrastructure for powerful syntactic transformation tools, then basic library revisions can be accompanied by automated source rewriting tools. We were pretty close to it in Smalltalk, without the annotations.
- weberc2 8y agoYes, but not all applications need that complexity either, so slim, simple tools are often really useful.
- hyperpallium 8y agoCurrently happening with JSON (instead of XML, instead of C0RBA) despite the brutality of ripping out comments to keep it simple. We now have json schema, soon jslt, json namespaces etc. To be fair, it's not impossible for some improvement to occur in this process.
- daxfohl 8y agoWhich really isn't so bad. Y eventually goes corporate, and is still presumably better than X, having learned from its mistakes. But for those who hate the new bloat, along comes Z and the cycle repeats itself. Chicka Chicka Boom Boom.
- osrec 8y agoBut we can learn from prior mistakes in each iteration and spring clean the software logic. I know it's a lot of effort to seemingly reinvent the wheel each time, but I like to think it does yield some benefit in terms of efficiency and cleaner logic.
- ellius 8y agoThis was a really funny experience for me as a self-taught guy going in the other direction. I started with Node in my spare time, and when I finally got a professional coding job my first project involved Java and Maven. I was kind of dreading it due to Java's reputation as this big bloaty terrible enterprise language, but once I actually got started I was like, "Man, this type safety thing and opinionated build tool thing etc etc are really nice." By no means is it (or any language) perfect, but a lot of the criticism suddenly seemed really overblown.