Just found the setting…thank you! It was actually driving me crazy. There’s still a bunch of really weird, unnecessary UX changes but this helps a lot.
My team of 5-6 devs has been using Inertia for a year now. I really don't think that Inertia is magic. Some of us have 10 years experience, some 2 years. I don't think anyone on the team has had to troubleshoot Inertia. Nothing with Inertia has ever broken. Juniors have never gotten confused by how it works.
It is just a simple bit of glue between your Vue app and your backend. The docs are good, and it overall just feels solid/stable. Super excited to see the new changes that are coming too!
There isn't one. There's been a couple attempts but they just don't hit the mark like Rails or Laravel do.
Honestly, the upside of 1 language is not that high. Don't be afraid of PHP, it isn't the same language it was 15 years ago. I've been programming JS for 10 years but only been using PHP for a year, it's weird but it's got some nice parts too.
That's a bad strategy. The reason people are tempted to mess with internals is that it works most of the time. Unless the library has some way of punishing people who use them, then they'll just do it without regard for, as far as they're concerned, arbitrary toothless restrictions. Sure, some stuff will break, but that's true even if they're respecting the API boundary too, especially for a beginner. There will be zero learning about API boundaries in particular.
I think it's fine to encourage beginners to engage with the internals of an API and do things that are unwise. The goal is educated pupils, not successful or maintainable projects. Let them play in the mud and get dirty. I think the idea that code is something that can be experimented with is one of the most valuable lessons, and breaking things is frequently the path to learning how they work.
Maintainability is one of the finer points that can come later.
Games are notorious for vendoring a dependency and never upgrading it again. If you use an internal API, it is not like you are forced to be on the upgrade treadmill where the sands suddenly shifted and the secret API does something different.
Seriously asking : how? I can't cheat my brain into not automatically seeing the next steps after that and the cascading relation between the all. Within a second or less.
A related if not the same thing I've been trying to do, especially with some DIY type work, is that it doesn't matter, deal with that later, just get this done thing for now.
I.e. not somehow trick yourself into not thinking about it, but just think who knows if/when I'll actually get around to that, for now just do this. Don't worry about optimal order.
If the skirting doesn't look as great as it could because I fixed and painted the doorframe first, only painting the wall and rest of skirting later, meh who cares, if it turns out to be that noticeable maybe I'll get around to giving it all another coat; in the meantime at least I got it done, not stuck in 'analysis paralysis'.
Are you skilled in the art of 3D development, perhaps feeling limited by the game industry’s scope? Join us at Stemble to craft atomic components and interactions that redefine educational simulations. We’re looking for a talented Three.js Developer passionate about leveraging technology for educational advancement. This role is perfect for someone who thrives in crafting detailed, immersive simulations, contributing directly to projects that make a difference in the educational sector.
The vast majority of Google+’s “growth” came from users of other Google apps who were pushed to convert their Google account to G+ but had no interest in using it otherwise, and they made the new Google account signup process push you into G+ even if you were just there for Gmail, YouTube, etc. They also counted a lot of activity in the apps people actually used as G+ interactions and refused to provide breakdowns for those stats, which suggests true interactions were really low.
Threads is not perfect but everyone on there had at least some genuine interest and anecdotally people see far more activity than G+ ever managed. I hear a lot of comments that both Threads and Mastodon tend to have more real interactions, too, and that matches my experience where lower follower counts still translate into more activity.
The difference is this is tightly coupled with Instagram which is one of the most active networks already and they can easily cross pollinate the two for a long time and keep sucking up people who get fed up with Twitter.
Frictionless importing of following/follower profiles. Frictionless account creation. Threads nudges in instagram feed, and prompts in Instagram menus about unread thread posts..
Yeah there was a certain set of news events that happened over the past couple months that turned X into a cesspool of people intentionally baiting each other and refusing to listen or show humanity.
Anecdotally Twitter traffic went _way_ down between 12/14 to 1/14. Seemed like a lot of people went on holiday vacation and didn't feel the need to come back.
In my social sphere, most just used it as a test run, but then Twitter became a centre of rage, violence, and politics that the more apolitical ones are spending more time on Threads.
In my experience it’s not quite the opposite but quite different.
Twitter is fine for apolitical people. They don’t follow the politics. And then Twitter is fine for people of a certain political leaning.
Everything else in this space is for people who are political + left enough to want to leave Twitter because they follow enough political things to be annoyed at all.
> Does downloads really tell us much or is it just a vanity metric?
It doesn't.
Which is why they won't reveal the new daily active users (DAUs) on Threads which is one of the most important metrics on user usage and tells us if they are still sticking to using the platform. The last time I checked it was less than 25M DAUs.
Not even the author is using their Threads account in the article as a contact and is still posting more on X than Threads.
Rspec/cucumber are great, but I’ve recently switched my app to minitest. It’s just as good for unit testing, and its system tests are a joy to work with. The setup and maintenance of rspec/cucumber isn’t worth it for me. It also makes it much easier for me to start new rails projects and get to my ideal workflow, because it’s the default workflow.
Just found the setting…thank you! It was actually driving me crazy. There’s still a bunch of really weird, unnecessary UX changes but this helps a lot.