Comments by "" (@d3stinYwOw) on "Theo - t3․gg" channel.

  1. Public money = public code is such a great idea. I wish Poland would embrace it more, not stealing opensc code for their ID thing, denying it, and then silently either obfuscating it, or removing entirely. Same with public transport systems - APIs should be public, but very few places on earth have it as well made, as Germany or UK :/
    568
  2. >Open source project >Discord Every single damn time. Use discourse or something similar, don't hide behind discord walls.
    62
  3.  @t3dotgg  well, in many cases FTP was enough for enterprises, so... :D
    60
  4. Video on HATEOAS/HATEOS would be great, waiting for it! Your channel teached me to not hate frontend development :)
    31
  5. There are exceptions of electron usage on linux - Telegram, ripcord, so it's possible to build native apps, which have any resemble of success. Other than that - I can agree :)
    17
  6. He won't get it, lmao
    15
  7. I bet he won't. It won't fit a narrative made in the video :)
    14
  8. He won't understand unfortunately
    8
  9.  @PhilipAlexanderHassialis  Or just windows environment is hostile to anything which is not endorsed by MS. Supporting windows for such projects is always a pain, not because those projects sucks, but windows environment is actively hostile for any meaningful usage - like needing admin for installing compiler, linker and stuff by MS or living mingw/msys2 life.
    8
  10. Rust also can build static single binary, but takes 10x more time, plus needs relying on muslc, which is not as loved as glibc in linux space :)
    7
  11. I totally agree with you - I'd first focus in 'how to start with OSS' A LOT on 'how to make good issues for project you like' instead of 'how to code'.
    6
  12. As of Zed, their work on Linux support goes really great. Initial supporting bits are there. Check their repo, you would be shook :D
    5
  13.  @ruaidhrilumsden  but the thing is, it's both possible and already done. QT has pushed forward a lot in terms of cross-platform usability. Plus, you're not forced to C++, and you can use Qt on Embedded devices. :)
    5
  14. Have your heard about vertical tabs extensions for other browsers? ;)
    4
  15. AGPL is not "Apache GPL" but Affero GPL. According to wikipedia: It is intended for software designed to be run over a network, adding a provision requiring that the corresponding source code of modified versions of the software be prominently offered to all users who interact with the software over a network.
    4
  16.  @thesenamesaretaken  Public API is kilometers ahead of whatever Poland have :P
    4
  17. For the case of Linux upgrade - they don't lie. It's like npm version bump for gatspy in that video. Simple. On linux it depends on your HW mostly, but gets better every day. And Electron is not everything here. We have QT, like Telegram app ;)
    4
  18.  @manoellopes211  Probably you didn't worked in a place where you needed to have at least task ID as part of commit msg ;)
    3
  19.  @SirusStarTV  google and opt-in? Weird way to spell 'opt-out'
    3
  20. FF or ladybird. But definitely not chromium.
    3
  21.  @alaskann  In that vein, yes. In general usage of closed walls behind login and/or without possibility to have publicly available chat log, like Discord, is bad for information preservation, to say the least.
    3
  22. What about Nim language? I think it should be also considered besides Rust, Go and Zig for creating useful tools efficiently. It's like marrying simplicity of Python, strength of Ada, typing of OCaml, with sprinkle of crazy metaprogramming capabilities and interchange-able GCs. You can even drop one if you want.
    3
  23. Better to be a bit radical than half-pushing the change.
    3
  24. Bringing SerenityOS PR on Ladybird, which got forked so much from built-in HTML viewer in SerenityOS that they STOP support for SerenityOS in Ladybird is dishonest as best. If QT succ on Mac, report bugs. Electron succ on more platform, but you will defend it, huh? Plus independent browser engine is huge. To not rely on whims of corpos is important today.
    2
  25. For AI tooling, bigger players like Copilot needs competition. I can see continue and codeium as great alternatives. Plus, locally running LLMs are gaining huge traction :)
    2
  26.  @hellowill  ADO is used, but not as publicly
    2
  27. Google dropped 'don't be evil', so... Plus, now I get why you bash so much on FF - google stonks.
    2
  28. @Rojfos I'm talking about PKP and "Mój Pociąg" app, and about opensc - eDO App and OpenSC Issue 1992
    2
  29.  @HansZimmer-b1r  Actually, self distributed APKs don't have limitations once they're signed ;) Plus, what limitation are you talking about?
    2
  30.  @Jonteponte71  Thing is - value was created, but without code. Code is not the only value, y'know?
    2
  31.  @ShrirajHegde  Plus, usage of cosmopolitan libc also might help in some cases, but dynamic linking hurts in Rust a lot.
    2
  32. Additional thing - they do fair pricing based on location. Great stuff.
    2
  33. Tickets, some code, blobs.
    2
  34. VSCode extensions are limited, unless you're microsoft & co. - you can't publish on official vscode marketplace extensions which use proposed APIs. For that - check devpodcontainers extension, 3timeslazy explained it quite well :)
    1
  35. That story about designers remember me about something - similar principle can be applied between testing team and SW engineers in general. In many companies those are in their own 'silos', which always makes me mad as hell, being test engineer who feel to be held back not by SWEs, but others within my 'silo'. When I started to bridge those gaps myself, everything went much better, both side. Less gaps = better.
    1
  36.  @slava_trushkin  They have docker option for self-hosting via docker-compose. It does not seem hard tbh.
    1
  37.  @dand4485  Well, currently CPU inference is gaining traction, as well as optimization of models to have them working on more modest hardware. As example, Q_4 7b model might take 'only' 8GB of RAM, and speed of content generation is also not that bad - on mobile R5 4800H I'm getting 4-5 tokens/second from such model on CPU only :)
    1
  38. Red hat won't give a coin about Redis. Why? Because Red hat got gutted out by IBM to just be an empty shell, a shadow of what it was.
    1
  39.  @sidma6488  Just like with FF. He and other can fix it, but it's easier to bash non-chromium competition.
    1
  40. Elon, ponzi scheme master with tons of hallucinations from ketamine overuse sues OpenAI of thing he said himself to close it? how typical of him. Google cannot currently compete with OpenAI on this field simply because of too much safety guardrails, like this hilarious post about refraining from providing C++ code or memcpy in C#.
    1
  41. Then set it properly and publish the config for it, to be sure that everybody have same pre-commit/pre-push setup.
    1
  42. I'd put it slightly differently - pick any VCS and learn at least a little about it. Git, mercurial, fossil... all count. Just use any of it.
    1
  43. Comment about pip from JS dev, kek. On the other hand, yes, we have issues with python as well, but I don't recall such bad handling from PyPI guys :)
    1
  44. Even I, total dumb person in regards to frontend development and web technologies, felt offended by this blog post.
    1
  45. As well as making it just a nick harder to commit without passing linter and formatting check, because, as good as editors are, people forget to format according to accepted way in repo. I can see it at work sometimes, where CI picked up that formatting was off, or lint, and next few commits were made just to fix those, already in PR.
    1
  46. >SVN >Out of date Not everything uses decentralized VCSes ;) Plus, Mercurial > Git ;) Other than that - teaching internals of VCSes on CS should be mandatory. Plus, using git to submit homework, or any other VCS, is great.
    1
  47. OpenTofu, search that up.
    1
  48.  @nicks8129  Mine too, lol :D
    1
  49. Just don't use crappy pre-commit engines like husky. use pre-commit, and have in CI just check as well. It's easy to have proper, repeatable environment, but you can't use JS :)
    1
  50. AV not being on par with Chromium. That's all.
    1