ratww

224 ms·

2101.
by ratww 7y ago
Someone on Reddit posted some more details. Apparently it's iLok removing the /var directory. https://www.reddit.com/r/apple/comments/d8nxhk/mysterious_av...
2102.
by ratww 7y ago
But I'm agreeing with you in all those points, like the sibling post said. I actually used OrmLite myself in some projects.
2103.
by ratww 7y ago
But Micro-ORMs are ORMs. And you're right, they do remove a lot of boilerplate.
2104.
by ratww 7y ago
You literally need the same piece of knowledge to to avoid that n+1 problem in both Raw SQL and ORMs: you have to use a join. Developers have been making n+1 mistakes with Raw SQL for years before ORMs became popular. It doesn't matter
2105.
by ratww 7y ago
Entity Framework and LINQ are amazing feats of engineering. Its query builder is super transparent, consistent and flexible, thanks to LINQ, but still generates very performant queries.
2106.
by ratww 7y ago
I worked in some projects where we had to support multiple databases. Entity Framework and a few Database Views helped us keep it agnostic. It was very common in the pre-cloud enterprise world. Uber did it recently, too. They changed from P
2107.
by ratww 7y ago
> I don't. I use sqlite for unit and local integration testing, and aurora-mysql for production. That's a recipe for tests that don't catch edge cases.
2108.
by ratww 7y ago
> you automatically invalidate one of ORMs biggest selling points which is being SQL-database agnostic 1. If the suggested alternative is writing only SQL from the get-go, then why would one even care about database agnosticism? 2. A lar
2109.
by ratww 7y ago
Yeah, I don't understand why developers feel they should use one over the other in every single case. I guess there's a certain appeal to only using nails or only using screws, but at some point it doesn't make sense to compr
2110.
by ratww 7y ago
SQL queries can be composed like in your example if you use subqueries.
2111.
by ratww 7y ago
I remember it being common in the 90s and 2000s, when DBAs were primarily developers. It's absurdly overkill if you're just doing CRUD, but if the DB uses some crazy schema that doesn't match the usage it keeps you sane. One
2112.
by ratww 7y ago
People can already buy on discount and resell later if they use Humble Bundle or stores that gives Steam keys. We have been able to do that for years.
2113.
by ratww 7y ago
That's the answer for me. The problem in those cases always the abuse of often obsolete OOP patterns and misnamed classes.
2114.
by ratww 7y ago
My point was that the commonly mocked VisitorObserverFacadeFactoryFactory Java idiom doesn't normally use generics at all. Of course you can mix generics with terribly named classes and OOP patterns, but that's hardly a problem wi
2115.
by ratww 7y ago
FizzBuzzEnterpriseEdition doesn't use generic classes. You're just making my point for me.
2116.
by ratww 7y ago
> You've probably seen the Factory<Factory<NaturalNumbersFacade>> joke somewhere, real live enterprise software is sometime like this, but unironically. I'm sorry, this is a terrible argument. That's definitely
2117.
by ratww 7y ago
This is a disingenuous argument. I work on some free software projects and most people don't even know who RMS is. There are multiple Free/Open Source software associations, projects and communities to choose, all with different p
2118.
by ratww 7y ago
Lyrics websites are just spam at this point. Whenever you search for song names they take the first two pages and interesting stuff such as news and interviews are scattered around the rest of the results.
2119.
by ratww 7y ago
The "don't walk into someone else's house" rule applies to ALL houses everywhere. You are explicitly forbidden to enter a house unless explicitly authorized. When it comes to website, there are billions of domains in the
2120.
by ratww 7y ago
When it comes to physical properties there's a huge difference between reading a banner posted in a street and entering the property to read some secret data: you have to be in different locations. That's why your analogy is compl
2121.
by ratww 7y ago
I'd argue that Auth itself isn't hard per se, but it involves hard things that you shouldn't roll your own, notably cryptography and session handling. But those are things that people normally delegate to either libraries (cr
2122.
by ratww 7y ago
Some people perceive Rails as being in decline. That makes a lot of people in the Rails community act defensively. I think it boils down to people only being experts in Rails and fearful of having to change to other tech. I used to get the
2123.
by ratww 7y ago
> You didn't "ask my server". You used a tool to extract data from my server. The tool asked the server. The server replied. > It's more akin to you standing just outside my property border and using a fishing pole
2124.
by ratww 7y ago
It's just a matter of what's available to buy. People just want to buy mementos to support their favorite artists. It's not that hard to understand. I'm pretty sure that if someone comes up with an album that's a fl
2125.
by ratww 7y ago
I think the problem with Haskell are not the concepts per se, but rather the terrible ergonomics (too many cryptic operators, point-free syntax, language extensions) and TERRIBLE learning material. Monads, for instance, are hard to invent b
2126.
by ratww 7y ago
I agree with you, but the point of the type systems is that they allow you to keep your purity while still giving the flexibility. A powerful type system is closer to a very powerful linter. Example: it is fine to have internal state in pur
2127.
by ratww 7y ago
Being from a rural town means your teacher options are limited. Having a family that is not musical or well-connected to musicians means you won't get recommendations and nobody knows if a teacher is good. Being poor means your teacher