I have spent a lot of time in the PL space and I just cannot wrap my head around the love of Racket. I absolutely love the innovation that comes out of the community though! The gradual types system work, nanopass, embeddable DSLs are all fabulous so I like to keep tabs on what they are cooking up.
I recently picked up Essentials of Compilation by Jeremy Siek, perhaps his book and lectures will make something click for me.
In the meantime Julia has been my happy medium for a “lisp”.
This depends on how you define ROI. Car infrastructure and lack of density reduces tax revenue for cities and strains infrastructure.
There are other human benefits to reducing car traffic and use in favor of public transportation:
* Reduces air pollution
* Noise pollution
* Allows a focus on human centric urban planning
* Allows for higher density commercial and residential increasing tax revenue
* Reduces pedestrian traffic injury
Unless you are actively managing your own herd or actively hunting I don’t see how you are connecting to nature at the grocery store.
People don’t care as long as it tastes good. The current methods we have for farming meat do not scale and we need to work on alternatives. Meat is tasty and people want to eat it.
Innovation will continue in the lab grown meat sector and when it eventually scales it will over take traditional methods. Current factory farming is anything but natural and there is plenty of harm being done.
I always love seeing more done in the web component space. I think Lit has the no build process captured pretty well and they include things such as a router.
I do prefer the style of of your components more, where you separate out the script and styles with html tags. I don't know if one way or the other is superior for performance, I but just like the separation verse the templated strings in Lit.
With build tools being so straightforward now-a-days, I struggle to see the value in the build less approach. One use case I can think of is maybe a constrained environment where the application contains some kind of customizable user components fully in the browser like a reporting WYSIWIG of some kind.
Is there a particular reason you prefer this approach?
I find that tools like Mermaid are pretty invaluable, especially when editing very large processes. Draw.io diagrams tend to get pretty unwieldy as they scale and editing inter process stuff if you forgot something quite frustrating.
Admittedly I primarily use D2 nowadays. The only features I miss in D2 from mermaid are the GitHub automatic rendering and Sequence diagram numbers. https://play.d2lang.com
I have seen this thrown around a lot, but I do not think it is true anymore.
V lang had a rough launch from what I can tell, with the author overselling and mistakenly underestimating the amount of work needed to fulfill their vision.
V still has a ways to go, but it is in constant heavy development with lots of contributors. It also has a wide gambit of interesting hobby projects using it.
I know this is a few days at this point but Bolero has been in active development. All development work was done on the now deleted streamrendering and v0.24 branches. Version 0.24 was just published today: https://github.com/fsbolero/Bolero/releases
If it allows for alternative design patterns that are simpler then I think it's a win in the end. For example pattern matching is great when writer parsers as an alternative to going the visitor pattern route.
Pattern matching has finally made it out of ML land and getting increasingly implemented in mainstream languages. I'm not sure if Rust is the main driver here, but I'm glad to see it.
I also found Superset unintuitive to use and setup as well. I settled on standing up Metabase because it was so simple to get started with trying it since it can be launched as a single jar. The business users loved it and so did I and administration with a Postgres backend instead of the internal h2 database was a breeze.
I started evaluating Defold this past weekend and I have been very impressed.
The developer experience is very similar to Godot, especially if you work on your scripts with external editors. Everything that has to do with building and running the app is faster than Godot though.
Initial builds with Defold are very fast, it has on demand hotreload, and very small binary sizes. The small binary size makes it well suited for working on web games.
The Godot Editor is still a tad bit nicer to use, but I do like the fact that the Defold editor is written in Clojure. I imagine it makes extending it fairly quick.
The main reason I see myself sticking with Defold over Godot is because scripting is done in Lua.
The Lua ecosystem has a lot history in the game dev space making it easy to search for answers. Lua is trivial to extend and has multiple statically typed options that compile to it. Notable statically typed languages are Typescript and Haxe. Also Lua has a lot practical use in many domains outside of the Defold editor unlike GDScripts lock-in to Godot.
Defold has no where near the size of the community of Godot, but the developers seem very active on the forum and GitHub.
I need to play around with it more before I’m 100% sold. Both Godot and Defold are great looking choices for 2D.
I don't really think anyone is copying anyone here. This is a popular feature for browsers that has been around for over a decade.
Orion[1] is another recent MacOS browser that released before Arc in 2021 and has vertical tabs. Edge had vertical tabs as an experiment back in 2020[2] and is full feature now. Vivaldi has had vertical tabs since 2015[3]. It might not count since it's not built in, but Firefox has had vertical tab extensions since 2007[4].
I guess it depends on how much bulk you are buying at once, but most bikes are compatible with a basket of some kind. A bike trailer could also be an option.
You may be confusing MiniLED and MicroLED. MiniLED still uses an LCD with multiple backlights and local dimming algorithms to improve contrast. MiniLED is pretty impressive and the quality of it is generally 1-to-1 with the number of backlights/dimming-zones.
MicroLED is more akin to OLED where each pixel is self emitting. MicroLED is almost the holy grail of displays and will more than likely obsolete MiniLED.
I really love Haxe. A truly multi-paradigm language with good support for GADTs, OOP, structural and nominal types, lambdas, and a lot of practical sugar on top. The macro system and abstract types add enormous flexibility that I miss when going back to C# or Java.
The language is a bit verbose, but I prefer it and generally add type annotations instead of using type inference (unless I’m dealing with a super gnarly generic type).
The language shines in the graphics space since some of the Flash community gravitated to Haxe. I’ve found that it works great as a client/server language similar to a typescript frontend/backend stack. The benefit with Haxe is that the backend isn’t limited to Node, it can run on JVM, bare metal with C++, Openresty with Lua, and anywhere Python runs. It’s pretty easy to implement F# style type providers with the macro system as well.
There is also a C# target, however, there are talks of deprecating. Hopefully we will see a revival with Reflaxe, another way to make new targets, or maybe even a CLR target. https://github.com/RobertBorghese/reflaxe
Lastly, I’m very excited about Ammer the universal FFI for Haxe by Aurel. https://aurel300.github.io/ammer/
My hope is that the community will rally around Ammer and bring in a lot of native libraries to all targets.
I recently picked up Essentials of Compilation by Jeremy Siek, perhaps his book and lectures will make something click for me.
In the meantime Julia has been my happy medium for a “lisp”.