beefsack

joined 1 year ago
[–] [email protected] 8 points 8 months ago (2 children)

One day, Valve will be under different ownership, and we will regret the time we fought for their monopoly.

[–] [email protected] 14 points 11 months ago (4 children)

In some cities they are, and it's a beautiful thing. An example is Canberra, Australia.

[–] [email protected] 2 points 11 months ago

It's such a cool editor, but after decades of Vim motor memory I just can't seem to wrap my head around the cursor / selection changes. I really wish there was an option to just make selection work like Vim.

[–] [email protected] 41 points 1 year ago (2 children)

Better than an ORM is to use a query builder. You get the expressiveness of SQL with the safety and convenience of an ORM.

Most developers that use ORMs create poorly performing monstrosities, and most developers who write raw SQL create brittle, unsafe and unmaintainable software. There is a happy medium here.

[–] [email protected] 8 points 1 year ago

Swift only treats Apple OSes as first class citizens - even though technically you can use it on other platforms it's a painful and limited experience.

[–] [email protected] 48 points 1 year ago (1 children)

This is only in the US I assume? The article isn't very up front about it.

[–] [email protected] 2 points 1 year ago (1 children)

It's nicer to post this as a straightforward feature request, rather than post some passive aggressive question asking why it doesn't already exist.

[–] [email protected] 2 points 1 year ago

My original account @[email protected] was when the project was announced 4 years ago (was either HN or r/rust) but to be honest I've only been properly using Lemmy for a few weeks.

[–] [email protected] 9 points 1 year ago (1 children)

Source is safely_endangered on IG. Original has an extra panel but I actually think this version is better.

[–] [email protected] 27 points 1 year ago* (last edited 1 year ago) (8 children)

I remember my time doing Ruby was really informative about testing and languages in general.

The Ruby community was really great at doing automated testing and it's actually where I really cut my teeth on testing, but if you go back and look at the tests you'll find heaps of them are testing and checking types for functions. It almost felt like people were building static typing using automated tests.

Some people bang on about static typing getting in the way of agility, but the reality is that you either end up spending the time creating extra tests, or you end up cutting corners and creating unreliable software which you'll spend a lot of time troubleshooting down the road. You end up paying a big price to save a marginal amount of time at the start of a project.