Speaking of which, how good is .NET on Linux nowadays?
I know it was possible for a long time (with the release .NET Core), but heard it was kind of broken/cumbersome on Linux. Maybe now it's easier to just develop an ASP.NET app, host it on Linux and use Posgres/Mysql instead of SQL Server?
Indeed, some folks found the feature unnecessary at first, but somebody found an OK way to implement it, and eventually it became popular enough that they decided to merge it back into mainline. Little drama and everyone is happy in the end. Actually I think this is more like the OSS ideal.
To be fair most of typing problems in Rails can be solved by having contracts and an operation pattern, kind of like Trailblazer, although they went a little bit too far lol
I'm writing a small side project app using Next.js. I found out the bad way that i18n support is quite bad. Sure, you get an i18n router, but you have to manage translations on your own. There are libraries to do it, which are fine, but translations only work in the front-end, there's no way to, for example, use translations inside an API call (!!).
Also, halfway through they decided to push a new Next.js version (still in beta) so you''ll need to move all your `/pages` to an `/app` folder, with a completely new structure.
I wanted to learn something new so that's fine, but something like Rails, Django or Laravel would have allowed me to develop way faster. I'm quite disappointed.
Can you elaborate on "manage translations on your own"?
I am working on dev-first localization infrastructure after being frustrated with i18n from a dev perspective myself. Your remarks seem like they fit into the infrastructure approach I am taking. See https://github.com/inlang/inlang
Playadito is great. There's a kind of Yerba Mate that is easier on the liver and stomach now called Cachamai, and there's some alternatives too. It normally comes in with extra flavors such as Mint, Orange, etc.
I'm Argentinian, been drinking Mate daily (sometimes several times a day) since I was ~18 (32 now) and that Yerba is great :)
Really? (Didn't have the time to listen to the talk.) I'd like to know if it was somehow measured, ie. how much of the Elisp code is still not adjusted to use lexical scoping and how much of such code would break by switching to lexical scoping. You can still opt-in to dynamic scoping by using defvar (and it's been a standard practice since forever), so the only scenario where old code would break would be where a called function accesses local variables from the calling function, like you would do in TCL with upvalue. I suspect that's a pretty small percentage of all the Elisp code in the wild; plus, this would be caught by the byte compiler, without the need to run the offending code. In any case: the change of the default is welcome, though not very important, as we've all already got used to putting `lexical-binding: t` at the top of every Elisp file :)
WSL is great. I use my personal computer for gaming, but I also like using it for side projects, and dual-booting is a pain in the ass. WSL makes it super smooth to have a proper dev env. I can use gvim from Linux just fine, with a bit of configuration I can even share clipboard.
I think it still has a few rough edges,but fortunately I haven't had to deal with those. Also recently they added support for systemd which is awesome. Most packages "just work".
I know it was possible for a long time (with the release .NET Core), but heard it was kind of broken/cumbersome on Linux. Maybe now it's easier to just develop an ASP.NET app, host it on Linux and use Posgres/Mysql instead of SQL Server?