It’s honestly the best of both worlds. A well built and tested hardware platform with well known specs and manufacturer support, that’s capable of running any third party software at the drop of a hat
It’s honestly the best of both worlds. A well built and tested hardware platform with well known specs and manufacturer support, that’s capable of running any third party software at the drop of a hat
Yes, but a better time was last month during the sale
Honestly I’d just stick to orca slicer
overwatch style
You mean team fortress style
Recently I had to do an update to the underlying environment a codebase ran on. This was a somewhat involved upgrade and took a longer period of time than most of our work usually does. I did it in a separate worktree, so I didn’t have to constantly rejuggle the installed dependencies in the project, and could work on two features relatively concurrently
It also provides some utility for comparing the two versions. Nothing you couldn’t do other ways, but still useful
And in elixir/erlang we’re spoiled with loads of options, from ETS to mnesia
During my most recent job search, the most annoying thing I saw was “resume consultants”
They’d reach out like an interested recruiter, but very quickly get to the sales pitch
Apple has done this many times before. Over even more frivolous patents (i.e. a glossy black rectangle)
They made their bed, now they have to lie in it
Seriously. I had a friend extolling how good his experience with his chiropractor was, in response to my tale about physical therapy after a skiing accident. I ended the argument pretty quickly by asking “how often do you have to go back”
I’ve only ever worked in one codebase that didn’t need feature flags, and even then we could have used them.
Graphite is ok, but honestly it’s a solution in search of a problem
Maybe if you have a massive pr, splitting it up like this works, but that’s really a planning failure. Stories should be smaller, and if you need to keep them separate for a long time, use feature branches
No. You’d use something like rev.2020 or some other wide gamut color space. Jxr already supports this, and some programs, like the Xbox, take hdr screenshots as jxr
Halo does it that way too
They can both model any color equally well, it’s just oklch works even closer to how we perceive colors changing. LAB and all derivatives are in Cartesian space, with luminance, a, and b being the defining axises. Luminance is self explanatory, but a and b are just axises of how much red/green and blue/yellow there is. It can be difficult to think of a color in how much blue it is, for example, when the color is something like nearly pure red. They both affect the hue output, so varying one can create strange, unintuitive colors
LCH works in polar space, like a color wheel. L is still luminance, c is the “colorfulness” and h is the hue. H and C let you set the same values a and b would, but in a more human way. We’re used to thinking about colors changing independent of how much of a color there is, and that’s what LCH does. Vary only the h and you get very different colors. Vary only the c and you get the same color but in different amounts of saturation, from full color to no color
For me the problem with AW, more than the boring gameplay loop, is the weird episodic format they shoehorned into it. You’d just be getting into the groove of the game, used to the annoying combat and stealth and such, and then it yanks you out of it and you have to watch an end of episode cutscene, and then a new episode cutscene, just to continue on
Control is awesome. I was hoping AW2 would be more like control, but from what we’ve seen in the media that doesn’t seem to be the case. Still holding out hope
True, however it occupies the same niche an ORM occupies, without the foot guns. Updating a slew of different db tables from rather clean and straightforward models is relatively simple. It tries to live somewhere between just doing everything as SQL and abstracting everything away like AR does, giving you conveniences from both approaches. You don’t get mired in scoping hell, but you don’t have big ugly messes of nearly-identical SQL statements either.
i’d recommend trying it out https://hexdocs.pm/ecto/Ecto.html
Data comes out as a map or keyword list, which is then turned into the repository struct in question. If you want raw db data you can get that too. And you can have multiple structs that are backed by the same persistent dataset. It’s quite elegant.
Queries themselves are constructed using a language that is near SQL, but far more composable:
Repo.one(from p in Post, join: c in assoc(p, :comments), where: p.id == ^post_id)
Queries themselves are composable
query = from u in User, where: u.age > 18
query = from u in query, select: u.name
And can be written in a keyword style, like the above examples, or a functional style, like the rest of elixir:
User
|> where([u], u.age > 18)
|> select([u], u.name)
None of these “queries” will execute until you tell the Repo to do something. For that, you have commands like Repo.all
and Repo.one
, the latter of which sticks a limit: 1
on the end of the provided query
I much prefer the repository pattern, as used by sequel and Ecto
Your models are essentially just enhanced structs. They hold information about the shape of data. Generally don’t hold any validations or logic related to storing the data. You perform changes on the data using changesets, which handle validation and generating the transaction to persist the data
It works extremely well, and I’ve yet to encounter the funky problems ActiveRecord could give you
I’d barely say they died. Doom Eternal is full of platforming, something a lot of reviewers winged about, and there are big undies like little kitty big city that fit the bill nicely, as well as the remake of SpongeBob Battle for bikini bottom