Readit News logoReadit News
felipeccastro commented on KDE is now my favorite desktop   kokada.dev/blog/kde-is-no... · Posted by u/todsacerdoti
blenderob · 3 months ago
XFCE or LXDE anyone? Honest question - If you use XFCE or LXDE or similar minimalistic DEs, are you happy with the choice? or do you feel somethings are missing that are available in KDE, MATE and the likes?
felipeccastro · 3 months ago
I've used XFCE for a 2011 laptop, it was about as fast as LXDE but better polished. Windows was unusable there, and XFCE made the computer feel brand new. Only the modern websites that would still cause slowness, but the OS was great.
felipeccastro commented on Type checking is a symptom, not a solution   programmingsimplicity.sub... · Posted by u/mpweiher
felipeccastro · 3 months ago
I have noticed that static type checking often enables people to build systems more over-engineered than they could without it. It's not a coincidence that factory-factory-impl happened in Java, not Ruby.
felipeccastro commented on Next.js is infuriating   blog.meca.sh/3lxoty3shjc2... · Posted by u/Bogdanp
motorest · 4 months ago
> I 100% agree. I've ran into the same issues, and I would never use Next.js for anything, and I will encourage every team at work to use something else.

Things will get far worse before they get better. Right now, online courses such as the ones in PluralSight are pushing Next.js on virtually all courses related to React. I have no idea what ill-advised train of thought resulted in this sad state of affairs but here we are.

felipeccastro · 4 months ago
The train of thought is “what is everyone using? I’ll use that too”
felipeccastro commented on Why Nim?   undefined.pyfy.ch/why-nim... · Posted by u/TheWiggles
dvfjsdhgfv · 4 months ago
Frankly, I'm surprised this is the only issue you bring up (I had many, when I first tried Nim several years ago - I think they were related to cross-platform GUI libraries for Nim, or the lack of them, or their awful state back then).

But LSP as a major concern? For me these little helpers are useful to catch small typos but I could happily do without them.

felipeccastro · 4 months ago
It's not just small typos, it's the ability to explore apis, the standard library, go to definition, quickly catch any error at the location it happens, not having to memorize large models and their field names, the list goes on.

I can work without an LSP, but when I'm searching for a new language that would be used by a team (including Junior devs) it's hard to justify something missing the basics of good DX. I haven't tried it with Cursor though, it might be less of a dealbreaker at this point.

felipeccastro commented on Why Nim?   undefined.pyfy.ch/why-nim... · Posted by u/TheWiggles
treeform · 4 months ago
I feel like Nim made me fall in love with programming again.

Nim fixes many of the issues I had with Python. First, I can now make games with Nim because it’s super fast and easily interfaces with all of the high performance OS and graphics APIs. Second, typos no longer crash in production because the compiler checks everything. If it complies it runs. Finally, refactors are easy, because the compiler practically guides you through them. The cross compiling story is great you can compile to JS on the front end. You can use pytorch and numpy from Nim. You can write CUDA kernels in Nim. It can do everything.

See: https://www.reddit.com/r/RedditEng/comments/yvbt4h/why_i_enj...

felipeccastro · 4 months ago
I agree with all your points but last I tried, the VS Code LSP was terrible. It’s hard to justify a new language when even the basics of autocomplete, inline errors and go to definition don’t work well. Part of the reason was that any function can be called on anything, which pollutes the autocomplete list.

Has the LSP situation improved yet? Similar issue with Crystal lang, which I enjoy even more than Nim.

felipeccastro commented on Web apps in a single, portable, self-updating, vanilla HTML file   hyperclay.com/... · Posted by u/pil0u
Sammi · 4 months ago
To take this concept one step further towards perfection, you would want to lose the backend completely and persist directly to a git repo using https://isomorphic-git.org/
felipeccastro · 4 months ago
And if keeping in local storage a list of all pages, you can create an index html automatically in a predefined format which makes it more of a database rather than loose documents.
felipeccastro commented on Poor Man's Back End-as-a-Service (BaaS), Similar to Firebase/Supabase/Pocketbase   github.com/zserge/pennyba... · Posted by u/dcu
throwaway032023 · 5 months ago
felipeccastro · 5 months ago
Not sure why this was downvoted, but I’d be very interested in learning how well does pglite compares to SQLite (pros and cons of each, maturity, etc)
felipeccastro commented on Rust compiler performance   kobzol.github.io/rust/rus... · Posted by u/mellosouls
norir · 6 months ago
Compiler performance must be considered up front in language design. It is nearly impossible to fix once the language reaches a certain size without it being a priority. I recently saw here the observation that one can often get a 2x performance improvement through optimization, but 10x requires redesigning the architecture.

Rust can likely never be rearchitected without causing a disastrous schism in the community, so it seems probable that compilation will always be slow.

felipeccastro · 6 months ago
It is ironic how “rewrite it in Rust” is the solution to make any program fast, except the Rust compiler.
felipeccastro commented on Malleable software: Restoring user agency in a world of locked-down apps   inkandswitch.com/essay/ma... · Posted by u/jessmartin
kylecazar · 6 months ago
I agree with all of the assertions about what software should be.

But... I think a lot of it already is customizable, and users don't want to configure. End-users (or doctors) hate having to learn more about software than they absolutely must. Just an example, Epic (EHR from the essay) definitely has the ability to mark fields as optional/required. Someone just needs to get in and do it, and they don't want to/know how.

The inaccessibility of config to laypeople may actually be where AI shines. You prompt an in-app modal to change X to Y, and it applies the change. A natural language interface to malleability.

felipeccastro · 6 months ago
This. Making something super customizable is a lot harder to implement (code being too generic, hard to reason about and debug) and often presents a worse UX ("why are there so many options??"). Having the UX design team interview and consider the needs of each user role interacting with the application, and ensuring the app displays/asks only the appropriate info for each user, hiding the rest and adopting smart defaults (instead of requiring everything), is easier to implement, safer and produces more intuitive interfaces than highly customizable ones, in many cases.
felipeccastro commented on Malleable software: Restoring user agency in a world of locked-down apps   inkandswitch.com/essay/ma... · Posted by u/jessmartin
mynegation · 6 months ago
Give me Delphi. No, seriously, give me Delphi, but for the web and in a modern popular programming language. Python would be great, but I will not turn my nose away from TypeScript or Go or Lua.

For those who don’t know, Delphi was (is?) a visual constructor for Windows apps that you outfitted with a dialect of Pascal. It was effing magic!

Nowadays the web ecosystem is so fast-paced and so fragmented, the choice is paralyzing, confidence is low. The amount of scaffolding I have to do is insane. There are tools, yes, cookie cutters, npx’s, CRAs, copilots and Cursors that will confidently spew tons of code but quickly leave you alone with this mess.

I haven’t found a solution yet.

felipeccastro · 6 months ago

u/felipeccastro

KarmaCake day172August 19, 2015View Original