@Kicko and... Trunks does the same as megalodon. It's not the screen size per se, it's the size change (different than orientation change) that causes issues.
@david_megginson it's not a matter of it working, I just don't like the experience of having horizontal real estate taken up on mobile. All of the apps (and many other mobile web sites) get this right and put the menus away at the top. Mastodon unfortunately does not.
Twitter/X has failed to send out payments to people who signed up for ad revenue sharing because the number of people who signed up βexceeded their expectations.β
This was the most predictable outcome of this misadventure. Elon who has failed to pay Twitterβs rent, employee severance or Google Cloud bill would suddenly have lots of money to pay users for tweeting? Yeah, right.
Here we got a class, in our regular #odata controller functions it produces #camelCase like we tell it to in our settings. However, in our non-base controller function it produces #PascalCase ... because, duck us?
Only on the expanded parts which are handled a little bit differently for efficiency, hense the need for the non-base controller function with odata.
@jab in both Newtonsoft.json and System.Text.Json, there is a way to control this behavior via "options" or custom converters. If it's part of your framework it might be obscured, but I would look for ways to adjust json serialization settings.
This article resonates strongly with me. I've been using Tailwind full-time for the last year, and I'm here to tell you it hasn't made my projects more maintainable or less complex. In fact, it's done the opposite; the only thing is delivered is short-term gains for long-term losses.
Tailwind is only ideal, in my opinion, if you're trying to build the same thing everyone else is, as fast as possible, and then never touch it again.
@peterdrake@jupiter I tend to think of the lowercase aliased types as "simple" types, in the sense that they are very easy to set, manipulate, and reason about, and are supported in serialization, databases, etc. Also, coming from Java, I'm glad there aren't both Integers and ints and I have to care about the difference.
We should not ignore the fact that the GOP is on track to nominate as its presidential candidate a man who is indicted on 78 criminal counts across multiple jurisdictions both state and federal. The GOP is broken beyond repair.
Since the introduction of nullable reference types in #dotnet I am observing extreme nullability phobia in many teams. They are going full swing, avoiding nullability at all costs which often leads to weird code and the misuse of the null object pattern.
It is still OK to have nullable types to convey that something may not be available.
@bitbonk wow, yeah, use the friggen ? already if a value can be left out. All that does is allow the code to behave as it always did before NRTs. It's everywhere where you're 99% sure you CAN'T pass a null that the NRT changes help you assert that.
Having spent the entire day battling with circuit disconnects when the JS work becomes to heavy for #Blazor I can honestly say it is now one of my least favourite web technologies
An AI prompt technique I learned to get to the point faster is always to end every prompt with βonly show me the codeβ. You wonβt get a wall of text then.
If you need an explanation, then ask for it afterward. #JetBrains
#qgis and #gischat I'm having a serious issue with qgis in which when my mouse cursor goes over any palette tool at all it acts like I'm clicking and dragging and messes up all my palette colors etc .. any thoughts?
If you write a blog article "Why you should never do X" and then you admit there are cases when doing X is valid you're immediately losing all the benefit of the doubt I had when I clicked on your article.
In 2001-02 during my consulting days, I built a web app that was running a profitable business. The customer wanted a feature he couldnβt afford, so he went bargain shopping.
The new folks didnβt know .NET, so they rewrote the whole app in Classic ASP and simplified the layering. They eliminated the Business Logic Layer, except that logic just went poof instead of moving into the UI or Data Access layers.
The company was out of business a month after that deployment.
@tylermumford@jeffhandley good point, but vanilla JS is not just older, it is also the underpinning of those other technologies, and has probably the most guaranteed lifespan of any technology available.
"The overall life expectancy of a programming language has dwindled in the past 56 years. A COBOL developer in the 1960s most probably retired in the 2000s, still writing COBOL. As a former professional VBScript, then C#, then Objective-C, later Swift, and finally Go developer, I can only see this trend accelerating. We should expect our favorite programming language to be replaced and removed from the market in a relatively shorter time every decade."
@deprogrammaticaipsum
> "We should expect our favorite programming language to be replaced and removed from the market in a relatively shorter time every decade."
This conclusion seems to be too broad. As the author acknowledges, C# has "replaced itself" (aka evolved) and seems in no danger of disappearing. Languages like Java and Javascript will exist at least as transpilation or VM targets for many decades to come. The only full replacements seem to come in closed ecosystems like Apple.