Skip Navigation

Posts
9
Comments
245
Joined
3 yr. ago

Press any key to continue... No, not that one!

  • Deleted

    ...

    Jump
  • Express, JavaScript (with JSDocs+TS for type-checking) and Postgres

  • So maybe switching providers altogether is a better option for those who have a choice

    Genuinely curious, how would it not be possible for a person to switch to another provider? Are people really so tied to gmail that they feel it's impossible to leave?

  • Ooh that reminds me. Been cranky all morning...

  • This is 👍. For those wondering, RFCs have been around for years in software engineering--since the beginning of the internet, practically.

    As a software engineer myself, I can confidently say they're a great way to build complex software in a more democratic way.

    They require a certain level of agreement and consensus, which makes them take a while to ratify. But you almost always end up with better software in the end.

  • I like TypeScript for its types and type-checking, but I also want to write JavaScript to avoid having a local build step, and having to wait for things to transpile/compile/etc when running locally. I have a pretty large project where I've gotten both worlds by just using JSDoc and only using TS for type-checking. VSCode still offers built-in type-checking with JSDocs and ofc the type-checking can also be run separately if needed.

  • Who are all these rich people who can just suddenly up and move the minute they don't like their state's policies?

  • Looks like a decent setup. Vanilla JS is the way to go for the best performance. Avoids vendor lock-in and those skills never go out of date. 👍

  • Take that, Stack Overflow! Programming.dev on deck!!!! Let's gooooooo

  • And also try to make tests that don't have to change if you refactor in future (although there are some exceptions)

  • Yeah I think this was hastily done to prevent the XSS injection attacks that were happening IIRC. They implemented encoding for content, but looks like they never got around to fully decoding it.

    Issue could've been avoided by just restricting the encoding to when the user types content in (and before database insertion), and decoding when showing the content in the UI.

  • Definitely. You'd love Allsides.com btw. Gives great info on how a topic is covered across the spectrum and summarizes them really well. There's an RSS feed for it too.

  • Yeah they'd have to maintain upgrades security patches etc and could get pricey depending on how much storage and bandwidth is involved.

  • Renovate is great. Plus there's just something about Github owning dependabot that always bothered me.

  • I wasn’t alerted that the post had been removed

    Are we supposed to get notifications for post removals? I'd be in favor for that.

  • What do you think of this?

    Think it's a terrible idea. For some reason people dont get that many of us are on the fediverse because we want to get as far away from anything that even remotely resembles, copies, piggybacks off of, or otherwise has anything to do with corporate-owned, centralized, ad-infested, user-hostile, privacy-invasive, social media platforms.

  • The issue with node is the single threading and having to scale with worker threads AFAIK

    People always say this but its not technically correct and can be misleading.

    Technically, JavaScript runs single threaded but not Node.js itself and certainly not when using it on the backend in something like Express. IO operations and other things tooling libraries do can cause you to run out of a thread pool. But Node.js, when handling requests, gives you much of the benefit of multithreading without having to deal with multithreaded code.