3 ms·
I understand and accept the reality of path dependence. At the same time, when I see projects like his, V8, HHVM, etc. I can't help but wonder where we could b
by munificent 7y ago
I understand and accept the reality of path dependence.
At the same time, when I see projects like his, V8, HHVM, etc. I can't help but wonder where we could be if all of that engineering effort had gone into more carefully-designed languages.
- cx1000 7y agoThere's always skip http://www.skiplang.com/ http://www.skiplang.com/ > Skip is an experimental programming language developed at Facebook from 2015-2018.
- hnakamur 7y agohttps://github.com/skiplang/skip https://github.com/skiplang/skip > The Skip project concluded in 2018 and Skip is no longer under active development at Facebook.
- TAForObvReasons 7y agoEvery language involves tradeoffs. The initial JS tradeoffs were ok for the target audience and environments. A "carefully-designed language" in 2019 might hold up for 2019 use cases but we don't know whether the tradeoffs will make sense in 2029
- peteradio 7y agoCan't we be reasonably sure it will be better than a weekend spitball? (The most successful spitball of all time to give due credit)
- munificent 7y agoThis is generally true. Most languages were carefully designed and if they are disliked now, it's mainly because we've forgotten their original constraints in which the language's design made sense. (For example, header files in C are a reasonable approach when your compiler can't fit an entire source file in memory.) But JS and PHP aren't that. They both have a lot of good ideas in them but they are also both hampered by lots of initial mistakes in their design. JS because it was designed so quickly, PHP because it was cobbled together ad-hoc by someone who wasn't focused on the design of the language. Semicolon insertion in JS doesn't represent a smart trade-off from the past, it was just a bad design whose author didn't have time to fix it before it hit the marketplace [0]. Likewise, PHP's wildly inconsistent core library names aren't a sign of some thoughtful hidden order. They're because Rasmus lazily used strlen() as the hash function for strings and wanted them to go into different buckets [0]. [0]: https://brendaneich.com/2012/04/the-infernal-semicolon/ https://brendaneich.com/2012/04/the-infernal-semicolon/ [1]: https://news-web.php.net/php.internals/70691 https://news-web.php.net/php.internals/70691
- vvanders 7y agoI mean Lua[1] exists, predates Javascript[2], is incredibly fast[3] and can be easily embedded[4]. I've personally shipped production game titles where the whole game state + logic was inside a 400kb block on a PSP where you only had 8MB of system ram, and this was before LuaJIT. Sadly, developer familiarity and ecosystem/mindshare sometimes dominate technical constraints, at least that's how we ended up with Javascript everywhere. [1] https://en.wikipedia.org/wiki/Lua_(programming_language) https://en.wikipedia.org/wiki/Lua_(programming_language) [2] https://en.wikipedia.org/wiki/JavaScript https://en.wikipedia.org/wiki/JavaScript [3] https://luajit.org/ https://luajit.org/ [4] https://github.com/vvanders/wasm_lua https://github.com/vvanders/wasm_lua
- BinaryIdiot 7y agoThis is what I always go back to. We have so many smart engineers working on ways to interpret JS to interact with native components and try to tighten that loop to make it faster. Why is there not a large movement to just make UI development in native languages better? Like, Swift UI looks great but it appears to be a huge exception to what everyone else wants to do. I'd love to see more work go towards making cross platform UI easier to do in native languages. I feel like you could get a lot more mileage out of that, especially if you add WASM as a compilation target, then you can get the same ubiquity that JS has.
- orange8 7y ago> Why is there not a large movement to just make UI development in native languages better What are these native languages you speak of?
- BinaryIdiot 7y ago> What are these native languages you speak of? Really any of them. Swift UI is the only example I can think of where a group of folks are working on making UI easy and intuitive to create and manage inside of a native language. Why is there not an effort to make something as intuitive in C++ or GO or Rust? C++ would probably be the hardest one, sure, and there are many UI frameworks for all of these languages but none of them are as simple or intuitive as Swift UI or how React / Vue works inside of JS. I'd love to see some more experimentation in ways of building UI in native languages. Heck, even in managed languages like C# or Java they could use the same type of treatment.
- eyko 7y agoThere are probably more JavaScript developers (not necessarily professional developers, just people writing JavaScript) than C++, Go and Rust combined, so it's just more likely that the ecosystem with more momentum will get more interest and resources. I'm sure Facebook could have written React Native in C, C++, Go, Java or Rust, but take a guess at what the adoption rate and the hype around it would have been... If Netscape/MS browser in the 90s had shipped with an embedded, sandboxed JVM with native browser APIs, then maybe the world would be very different today, but we work with what we have don't we all?
- lootsauce 7y agoIt's a perfectly valid sentiment but... Comments like this annoy me because, as I get older (turned 40 this year surpassing 20 years of web development) I've noticed variants of it come up many times a year in various contexts and it often feels like so much useless hand wringing and lamenting. In my experience shoulda, coulda, wouldas will get you bupkis in this world. Kinda like how a great idea is worth pretty much nothing. The problem is much bigger than the design of a language, the problem is producing something (not a language) people will use and growing software systems that meet varying demands as those products evolve in a way that is affordable. Of course there are all sorts of tradeoffs to make these things happen, most of which have nothing to do with idealized whiteboarding and language design. That stuff often irrelevant when you take into consideration all the various kinds of other situation-specific details people face to make things lots of people use. That goes the same for products and for languages. And of course the two classes of processes co-evolve. Further, language design does not imply better products. It is tangential to all the other things that make a product happen. You have to hire good people, you have to identify meaningful problems and provide better solutions. You have to get it in front of people and you have to adapt over time to your core audience's needs. Use lua use php use C# whatever you do all your choices including that one need to be self supporting of each other. The developers have experience in x, y is what runs on the platform, devs more often know a than b and so are cheaper to find. Language design matters not in those scenarios. Not defending any language design or any technical choices over others here at all, just saying if you want to see a change in the state of things sentiments like this are more like eating popcorn while you watch the world go by. Kind of like when you have an open source project and get requests for fixes but no pull requests. The most viable open source is build by a community of collaborators and is easy for new collaborators to join in and contribute to. If you don't have a community of users that care about your project it does not matter what technical decisions you make, what language you use and what design it follows. So what matters more than language design is problem solving and community and getting more pull requests than the other guy, more conversions than the other app and shoulda, coulda, wouldas are popcorn on the theater floor.
- munificent 7y ago> it often feels like so much useless hand wringing and lamenting. Not every comment on the Internet needs to be actionable, but sure. > Further, language design does not imply better products. That's fair, but we aren't talking about products here. We're talking about an announcement of a language implementation. Jazz records won't cure cancer, but that doesn't mean we can't talk about jazz. Not defending any language design or any technical choices over others here at all, just saying if you want to see a change in the state of things sentiments like this are more like eating popcorn while you watch the world go by. My day job is working on a language, for what it's worth, so I can both eat popcorn and work to change the state of things.
- snek 7y agoI'd like to introduce you to my religion. https://webassembly.org/ https://webassembly.org/
- ceedan 7y agoEven carefully designed languages have mistakes.