thomasfortes

Above like $500, they all play pretty much the same

Yeah, really cheap guitars (like $150 cheap) can be great but they also can be terrible due to non existent QC and electronics and hardware being the cheapest available because every cent matters.

But as soon as you hit a price point where QC exists a lot of reasonably priced instruments just need a proper setup and better electronics (not the pickups, but pots, wiring and shielding, the cheapest mods that you can do in a guitar or bass) to feel like a professional instrument that you can use in any situation.

And you are dead on on yamahas, if you play a pacifica you can be sure that almost every single pacifica of the same model will feel very closer, yamaha consistency and QC is amazing at their price point.

Yes, you can and I know just enough of cars to not be scammed by people, but not to know how the whole engine works, and I also don't think that you should learn everything that you can learn, there's no time for that, that's why I made the bird view comment.

My argument is that when you have at least a basic knowledge of how things work (be it as a musician, a mechanical engineer or a scientist) you are in a much better place to know what you want/need.

That said, smart and motivated people thrive if they are given the conditions to thrive, and I believe that physical interfaces have way less friction than digital interfaces, turning a knob is way less work than clicking a bunch of menus to set up a slider.

If I were to summarize what I think about AI it would be something like "Let it help you. Do not let it think for you"

My issue is not with people using AI as a tool, bit with people delegating anything that would demand any kind of effort to AI

Last weekend I was arguing with a friend that physical guitar pedals are better for creativity and exploration of the musical space than modelers even though modelers have way more resources for a fraction of the cost, the physical aspect of knobs and cables and everything else leads to something that's way more interactive and prone to "happy mistakes" than any digital interface can offer.

In my first year of college my calculus teacher said something that stuck with me "you learn calculus getting cramps on your wrists", yeah, AI can help remember things and accelerate learning, but if you don't put the work to understand things you'll always be behind people that know at least with a bird eye view what's happening.

Using GRiSP Metal, not exactly without an OS, but using a real time OS designed for embedded devices.

https://www.grisp.org/software

Nine Sols was clearly built on top of Hollow Knight, but my take on the combat is a bit different, Hollow Knight and Nine Sols would be like Dark Souls/Elden Ring (HK) and Sekiro (NS), one is focused on fast movement and dodges while the other is more focused on parry and counter attack mechanics.

I enjoyed both games but I found that with the exception of the last boss Nine Sols was a way easier game after you figure out how to parry effectively.

I also enjoyed the whimsical art style of HK a bit more than the (as said in a comment) "taopunk" style of NS, but that's purely subjective.

But if you enjoy metroidvanias both are great games that you should try.

Android has granular control over notifications, which is great because some apps that I need send a lot of marketing notifications that I don't care about but I cannot get rid of essential notifications.

Not all apps do it and some push all notifications through a single channel (and some manufacturers hide the granularity options in advanced settings, I'm looking at you Samsung) but at least it exists.

The soldered ram was necessary for Strix Halo

In the LTT video the framework CEO explains that AMD wasn't able to make LPCAMM work because of signal integrity over the bus reasons.

But 2000 dollars for up to 110GB of VRAM in Linux makes this a VERY interesting little machine, so much that the framework website has a cloudflare queue right now...

it's not exactly a case of 'lost their original vision'.

Considering that one person that says that he worked at the beginning of the project writes that the original idea wasn't to compete with flathub and given the current state of affairs I would argue that the project today doesn't have the original vision anymore.

As for creating a ton of projects, today with LLMs I'm pretty sure that I can write code that scrapes github repos for installation instructions and use it to create thousands of packages for everything that can run in Linux, doesn't mean that I should because there would be no quality control at all.

It is a noble idea to create packages to help create critical mass, but even with simple packages, seven hundred are more than anyone can use specially when we're talking about software that most likely have a GUI, and if you never really use most of the packages that you create you are bound to create these issues with QA.

All of that could be avoided (or minimized) if the fedora project created two flatpak repos, one for core software and one for contrib software, but that probably would be clear competition to flathub and probably be mostly ignored.

Hey, here they are :)

Original vision https://pagure.io/fedora-workstation/issue/463#comment-95406...

Person with more than 700 packages https://pagure.io/fedora-workstation/issue/463#comment-95541...

As for the C&D, the github has some issues with Fedora distros and labeled as "Dependency issues" and there's no indication if the user is using the fedora flatpak or the flathub one, so if I had to guess I would guess that they aren't that happy with:

    1. Being asked to fix bugs introduced by downstream.

    2. Having their brand damaged because it isn't clear that the fedora 
       flatpak is a way more limited version than the verified one.

    3. Having their issues with their complaints minimized and ignored by
       the people responsible for the fedora flatpak system.

One of the comments in the main thread says that the original vision for the fedora flatpaks was to be mainly for things that fedora wanted to have tight control and be preinstalled in their distros (Firefox, LibreOffice, GNOME and apps, etc...), which makes a lot of sense, but at some point it lost their original vision and started packaging everything under the sun.

In another comment someone says that most of the extra packages are maintained by a single person (more than 700), there's no way a single person can validate and test all these packages (or even use them).

You're stuck with cloudflare nameservers¹, so if you want to change nameservers you need to transfer them to other registrar, how much of a deal breaker this is is up to you, to me is project dependent.

1. Section 6.1 of https://www.cloudflare.com/domain-registration-agreement/

Integrating javascript with liveview and pushing and receiving events from client to server (and from server to client) is pretty simple using hooks: https://hexdocs.pm/phoenix_live_view/js-interop.html#client-...

The AI story is mostly centered around the Nx project: https://github.com/elixir-nx/

I’m wrong but I’m struggling to think of a killer feature of Twitch or an aspect of the overall experience that’s better than YouTube Live videos.

Discoverability, content creators and community.

Live streaming is a second class citizen on youtube, and as such it is hidden under dropdowns, the live streams aren't always on the top of your followers, live recommendations are worse than useless and the big creators that move to youtube do like Ninja with Mixer, with a big fat paycheck to justify the loss of viewership and community.

Yeah, a PS2 controller has a graveyard at the center when compared to a PS5 or series controller, just grab a cheap USB controller from Amazon and use some tool to see the precision of modern controllers.

That said, unless conventional sticks get way cheaper I'll stick to hall effect ones.

At least for Xbox controllers and headsets (and logitech lightspeed mouses too) they don't use bluetooth, they use a proprietary protocol, you can connect them using bluetooth but if you really want low latency you will need a proprietary dongle.

I suppose sony do something similar, and as far as I know they all use the 2.4GHz band.

Good thing both Xbox and Playstation controllers have a 3.5mm jack and I don't need to buy their overpriced shitty headsets to play without significant audio latency.

Also no shared memory in processes and they all communicate strictly through message passing, so running a piece of code in the local node, in another node in the same machine or in a node on the other side of the planet is a matter of telling which pid you want to send the message to, the BEAM will figure out how to send the message to the correct place in the cluster and your program will be none the wiser.

Something like this: https://fly.io/docs/reference/dynamic-request-routing/#the-f...?

You probably would have to handle a lot of the logic by yourself for privacy and security reason, but I think this is a nice primitive to start from.

It's a play on https://en.wikipedia.org/wiki/Greenspun%27s_tenth_rule

Virding's Law: Any sufficiently complicated concurrent program in another language contains an ad hoc informally-specified bug-ridden slow implementation of half of Erlang.

A couple weeks ago a client asked for some stats that came out of the blue (the data was collected, but they weren't exposed at the dashboard), his app was at fly.io, I've set up a wireguard tunnel to connect a livebook to the app and we went in a couple hours exploration of all the data that wasn't exposed at the dashboard, I took a ton of notes and the client spent a lot of time gushing about how he never had that much access to the underlying data in projects before without having to wait at least a couple weeks, to be able to work with live data almost instantaneously is a plus that I don't know if I'm able to give up at this point.

It was a new client and a short project but since then they closed a couple years contract to a new project, Livebook is indeed magic.

When working with livebook the usual library for graphics/plotting is vega_lite.

https://github.com/livebook-dev/vega_lite

Hear the same thing about beats, too much bass.

Anyway, the point still stands, Beats is considered a fashion brand, it was used by athletes all around the world a couple years ago, now athletes are all in on apple airpods and it's been a while since I've seen someone talking about buying a beats.

Isn't Beats by Dre considered not top of the line when it comes to sound quality and more like a fashion brand?

I'm not saying that they are bad, just that they aren't at the same level as brands like bose and sennheiser which are way less focused on celebrities branding.

They moved from Go to Rust.

https://discord.com/blog/why-discord-is-switching-from-go-to...

From the discord blog posts it seems that elixir powers the chat system, with rust and python as the other two main languages in their stack.

As for whatsapp, they are mainly a erlang shop and yesterday they open sourced a type checker for erlang:

https://github.com/WhatsApp/eqwalizer

The people working on BuckleScript had been unhappy about syntax for a while, and wanted to make it simpler for people coming from JS.

Yeah, but as far as I remember the new syntax and all changes were discussed and developed behind closed doors and dropped like a bomb, I mean, it is their project and they could do whatever they want, but two points left a pretty sour taste in my mouth:

1. You know that there are a lot of native projects and your changes will cause ripples through the entire ecosystem, warning people would be nice, they have no obligation to do so, but they can't really complain that people were pissed about it.

2. The rename and using all the old bucklescript resources instead of passing these resources for the community and saying "ok, now we're working on ReScript, it is a new language that follows our long term vision for the future of webdev, follow us". They own the project, but they don't "own" the community.

I didn't hang around on the Reason discord (for good reason, I now suppose :P)

Yeah, it wasn't a nice place.

As for reason dying out, most of the devs that embraced native ReasonML were also OCaml devs and tooling was being developed to facilitate the transition from web to native code with the more approachable syntax of reason (esy.sh and revery were two of these initiatives).

ReScript dropping support for OCaml was like "ok, no point in trying to bring web people to native now, let's stick with OCaml syntax, they aren't the same language anymore".

And as "my side", I did use Reason syntax in native just because I was already using the syntax in web projects, otherwise I would just write OCaml, but after seeing how the changes were announced I gave up on Reason for web and didn't even bother with ReScript, don't get me wrong, it is a really nice language for webdev, but I have no interest in waking up in a Monday just to discover that the language I'm using is being completely changed without any warning in the next week.

Agree with you, Reason is effectively dead, the "drama" part is that the decision came from nowhere, leaving the native devs with a sour taste and the frontend devs with a "Hey, we just changed the syntax without warning and will not support the old one anymore, good luck", which made me move all my projects out of reason ASAP, if the developers can pull out giant changes like that without warning, sorry, I will not use it, too unpredictable.

Also, rebranding instead of starting a new project sounds just like "it's my baby, I'm gonna kill the old project so no one that disagrees with my decisions can continue it".

Some people in the Reason world blame the ReScript people for this, which I think is entirely misplaced.

I mean, the way that the creator of ReScript behaved on discord to any criticism to his decisions at the time didn't helped...

Funny thing, ReasonML (the alternative syntax for OCaml) was created by Jordan Walke, who also created React.

The cool thing about Bucklescript is that it generated pretty readable javascript, so dropping the compiler and working with the JS files was pretty easy, which is what I did with a project that I was working when the drama started, just used the generated js files and slowly replaced them with typescript when needed.

The creator of bucklescript (ReasonML/OCaml to JS compiler) decided to drop ocaml support and gather the already built community around his new project (Rescript) and it wasn't well received by the part of the community that were interested in ReasonML (and OCaml) for native or hybrid applications, which is kind of obvious since:

1. Rescript is not ReasonML/OCaml, it is a new language.

2. Rescript doesn't compile to native code.

Forks were being discussed, the creator didn't like the criticisms of his decision (which came as a surprise for most of the community), people didn't liked having the rug pulled out of their feet, aggressive comments were made, people were angry and the community got separated between web and native, both weaker than the united one.

TL;DR; The creator decided that his project was for web only, alienated the native developers out of the blue and shattered the community.

If I had to bet, I would guess that the ReasonML > Rescript drama/change killed a lot of the momentum in the community.