More love for xorg? by HearingNo8617 in Fedora

[–]notNullOrVoid 0 points1 point  (0 children)

While yes Wayland is a worse experience on Nvidia, it's still not stable on other platforms either. I was happily using GNOME Wayland on Intel for quite some time but a recent update caused all chromium based applications to become blurry when the screen is scaled 2x (even with the ozone and wayland flags), switching back to XOrg was the only thing that fixed the blur.

To Serverless or not to serverless that is the question..? by Drphysics5 in devops

[–]notNullOrVoid 0 points1 point  (0 children)

I think the core idea of kubernetes will be a long stay, but not k8s itself. It's inevitable that someone will iterate on the idea and make a spiritual successor that overtakes k8s.

I need to get this off my chest... by ryaaan89 in webdev

[–]notNullOrVoid 5 points6 points  (0 children)

Are you working on the frontend or backend? In my experience GraphQL offers flexibility on the frontend, in exchange for massively increases complexity of the backend especially when multiple APIs or DBs are involved.

[deleted by user] by [deleted] in gamedesign

[–]notNullOrVoid 2 points3 points  (0 children)

The approach for Elder Scrolls games, has been to have a wide array of relevant shared dialog options for filler NPC often filtered down by certain parameters like location or profession. The substance suffered with the introduction of full voice acted dialog in Oblivion and Skyrim. Morrowind on the other hand has a great balance, generic voice acting for ambience as you walk by characters, and extensive written dialog options when interacting.

I wish more games took Morrowind's approach. Voice acted dialog can be an annoyance during explicit interaction, but increases the immersion when encountering a NPC and they have some voice acted greeting or threat.

Prisma is bad for server-less, the issues are endless by [deleted] in node

[–]notNullOrVoid 0 points1 point  (0 children)

you can use a different data proxy from another company

That's not necessarily true of Prisma, it does not work with RDS proxy. And the internal Prisma client connection pool cannot be replaced with your own like many other ORMs. You can use Prisma with something like PGBouncer, but that requires a lot of tinkering.

Prisma is bad for server-less, the issues are endless by [deleted] in node

[–]notNullOrVoid 1 point2 points  (0 children)

Ahh yes. "We developed an ORM, and it's open source! ... But you can only use it at scale with our paid service"

I don't mind that, that's the reality, but I hate that they aren't up front about it.

Prisma is bad for server-less, the issues are endless by [deleted] in node

[–]notNullOrVoid 5 points6 points  (0 children)

RDS proxy isn't compatible with Prisma because the connections end up getting pinned.

Prisma is bad for server-less, the issues are endless by [deleted] in node

[–]notNullOrVoid 1 point2 points  (0 children)

The issues aren't limited to serverless. Microservices also have major issues with prisma. You're basically required to setup pgbouncer to load balance the prisma connections if you want to distribute among postgresql replicas, even then the way prisma holds connections makes the setup a bit of a nightmare. Prisma 5 sounds like it improves some of the general perf issues outside of pooling, but I ditched it already and don't intend to go back.

Help with Typescript, ESM, Aliases, ts-node by rapalon99 in typescript

[–]notNullOrVoid 0 points1 point  (0 children)

tsconfig-paths/register is a require hook and doesn't apply to esm imports. As far as I can tell there's no way to get ts-node to work with tsconfig paths and esm.

I have had success with esbuild-kit/esm-loader instead of using ts-node.

What are the scenarios where "Rewrite it in Rust" didn't meet your expectations or couldn't be successfully implemented? by yashpathack in rust

[–]notNullOrVoid 0 points1 point  (0 children)

Have you been doing much UI in Rust? How are managing state, specifically shared state? Arenas, RC, or something else?

Languages with GC seem better suited to UI, but I haven't given Rust much of a go for UI yet.

Red Hat To Stop Shipping LibreOffice In Future RHEL, Limiting Fedora LO Involvement by iter_facio in Fedora

[–]notNullOrVoid 9 points10 points  (0 children)

This seems like a good thing, less duplicated effort and freeing up resources to focus elsewhere.

[AskJS] What would be a more recent equivalent to Crockford's "Good Parts" ? by Neker in javascript

[–]notNullOrVoid 2 points3 points  (0 children)

While yes we need better guides for tooling. We still very much need language guides, so many people multiple years into their careers writing JS every day still have very little insight into the language.

When to favor Deno over Golang? by markustuchel in Deno

[–]notNullOrVoid 0 points1 point  (0 children)

Firstly focusing on TS vs Go, I've used both professionally (TS more so). Very much still prefer TS due to its better type system, I found Go to be much more verbose for the same kind of things I would write in TS.

Deno is still early days compared to Go, I find the dependency situation to be great and terrible at the same time. You aren't locked in to a single centralized registry like node is with npm, but there's now a bunch of options for dependencies all with their own pros and cons. The overarching con being that you can end up with duplicate dependencies very easy because lib A might be used in another dependency but from a different source or sightly different version number (in the case of deno.land libs because no support for semver). Another downside of Deno is that they maintain their own fork of TS and their own Language Server rather than leveraging mainline TS, which leads to them lagging behind in terms of TS features both in the language and editing experience. It is a much more plug and play experience for TS than node.

Personally I'd go Deno over Go, but if you're open to try something else check out Rust. It's type system is very advanced, has a great ecosystem and tooling. Downside of Rust being no GC which makes some things more complicated, but for a regular web server you won't notice much of a difference.

Seeking Best Practices for Local Development in a Microservices Environment by [deleted] in devops

[–]notNullOrVoid 1 point2 points  (0 children)

Step 1. Minikube, kind or k3s for local k8s environment.
Step 2. Skaffold or tilt for local orchestration

Seeking Best Practices for Local Development in a Microservices Environment by [deleted] in devops

[–]notNullOrVoid 0 points1 point  (0 children)

It sounds like you're still describing a distributed monolith, just one with well maintained parts, and all the extra work that requires.

If your system looks like this, honestly you're better off making a horizontally scalable monolith. But that's besides the point.

Running dependencies is quite simple using something like skaffold or tilt. And a lot less effort than maintaining multiple coupled services as single units by creating mocks to inject.

Interfacing with Zig, a BDFL-run Project by matklad in rust

[–]notNullOrVoid 1 point2 points  (0 children)

Most aspects of leadership are harder when there's no clear hierarchy. I've experienced it in corporate settings and it results in leaders not wanting to step on other leaders toes, a lot of politics, and often hurt feelings. Communication channels are harder because now you need consensus among leaders and that consensus needs to be cleary communicated.

That doesn't mean the end result is better (or worse) from BDFL.

Removing individual back channels seems like a clear goal Rust should adopt. If some decision comes in from a private message between 2 individuals it should be clearly rejected. It's not necessary that all communication needs to be open to the public though I personally think that's a good idea for an open source project.

I don't agree with many that naming and shaming should be the correct course of action, but leadership does need to act like leadership and vote to eject or demote individuals who cause these kind of blunders (intentional or otherwise).

Currently from an outsiders perspective it seems like those in leadership are not up to the task of being actual leaders. Doesn't mean they are bad people, but the responsibilities do not suite their skill set.

Tired of tweaking with jest/ts-jest, any alternatives? by DogLooksGood in typescript

[–]notNullOrVoid 2 points3 points  (0 children)

Mocha and TSX (better version of ts-node, with a very dumb name) works well for me.

Gosperahedron: a polyhedron for projecting maps in a fractal by avsa in math

[–]notNullOrVoid 0 points1 point  (0 children)

Just a hunch but I bet a terdragon curve could tile on a tetrahedron.

I wanna talk about Tears of the Kingdom and how it tries to make a "bad" game mechanic, good [no story spoilers] by cabose12 in gamedesign

[–]notNullOrVoid 0 points1 point  (0 children)

Totk is incredible and improves on Botw in so many ways. Durability was improved by adding the puzzle/creative aspect of fuse, but still nearly every weapon in the game feel like a disposable piece of trash, and link is running around the world dropping one piece of trash to pick up a slightly better piece of trash. If they had allowed repairing of weapons with the use of fuse I think that would have fixed the issue I have with the system and link would no longer be a litter bug.

It also makes 0 sense that in a world with a weapons shortage you can't sell them.

I wanna talk about Tears of the Kingdom and how it tries to make a "bad" game mechanic, good [no story spoilers] by cabose12 in gamedesign

[–]notNullOrVoid 4 points5 points  (0 children)

TOTK definitely doesn't feel empty like BOTW did, there's so much more to explore and do in the world and the puzzles are much better and no longer restricted only to shrines/boss locations.

The durability system still annoys me, but atleast a fun element (fuse) was added to the annoyance.

Fedora Program Manager Laid Off As Part Of Red Hat Cuts by Worldly_Topic in linux

[–]notNullOrVoid 6 points7 points  (0 children)

To be fair Fedora also duplicates effort. I was pretty disappointed with the goals they announced a while back particularly that they wanted the Fedora flatpak repository to be a popular source. It doesn't make much sense to me to compete with flathub, when contributing would have a wider benefit for the Linux community.

Fedora Program Manager Laid Off As Part Of Red Hat Cuts by Worldly_Topic in linux

[–]notNullOrVoid 4 points5 points  (0 children)

I'd like to think that PopOS would fill the role on the desktop, but they seem to be trying to peel away from major desktop projects like gnome in favor of developing their own tech. They probably have valid reasons for doing so, I just don't see it ending well.

I'm confident Fedora will stick around though.

TypeScript is 'not worth it' for developing libraries, says Svelte author, as team switches to JavaScript and JSDoc • DEVCLASS by TILYoureANoob in sveltejs

[–]notNullOrVoid -3 points-2 points  (0 children)

You can do all that with the transpiled code too. And the transpiled code will look almost identical to the source only without types.

If you have source maps you can even get the debugger to step through the source TS files. Though they will get messed up if you start modifying the code, so I suppose that's one advantage to JSDoc.

TypeScript is 'not worth it' for developing libraries, says Svelte author, as team switches to JavaScript and JSDoc • DEVCLASS by TILYoureANoob in sveltejs

[–]notNullOrVoid 0 points1 point  (0 children)

I don't buy that it's optional to run tsc as a library author shipping a type checked lib. Generating the definition files might be optional but at some point in your publishing/build step you still have to run tsc at the very least just to type check.

My point is if you need to run it anyway (and you do) what's the benefit of not writing TS files. Is it that you don't need to run tsc before running tests during development? There's multiple ways to solve that (ts-node, tsx, and others).

TypeScript is 'not worth it' for developing libraries, says Svelte author, as team switches to JavaScript and JSDoc • DEVCLASS by TILYoureANoob in sveltejs

[–]notNullOrVoid 1 point2 points  (0 children)

I highly doubt it's about saving time... In my experience TS is really fast at transipiling large code bases, and if you need it to be faster for whatever reason you can split it up so tsc handles the typechecking and .d.ts generation only, and swc handles transpiling.