drop table /;

@Grumm it won’t — because of their design and weight-to-volume ratio, iPhones are fragile again. 10, 10s and 11 pro were the toughest iPhones ever, and this design isn’t coming back.

@Grumm maybe someone had an iPhone with linux installed.

@Grumm I’m literally talking about 14 pro being inferior

@K-ASS 11 pro has the same bouncy round shape as 10
12 and up are different though, it’s rectangular

@benj js on the backend, duh

Subscribe to Patric Warlde. This guy knows stuff.

Get this disgusting scum off my platform. I use HTML, CSS and raw JavaScript.

@Parzi I know. And that’s why it was so enjoyable — it’s very thin and light

@Parzi I didn’t have money to by an iPhone back then >_< though I later bought iPhone 6 to my younger brother as a gift, and yes, it’s quite a pleasant device to use. The battery life is on a shorter side tho, that’s a bummer

@Parzi cases make HUGE difference, especially the soft ones. Any drop resistance problem can be solved by a proper case. My problem is I hate cases. I want to hold and enjoy an astonishing piece of engineering as it was meant to be, not obscured by anything.

@Grumm I broke a screen on my Nokia 3220 back in the day, but that’s it. My IPhone also survived asphalt several times.

Before you say it, yes, I had Nokia 3310 back in high school. It completely disintegrated every time it hit the floor, battery out, back panel off, front panel off, keyboard flying. Had to collect all that stuff and reassemble it. It stayed alive though

@Oktokolo thanks
@immutable for my neurotypical colleagues, I mostly use three-point estimation, I found it to be quite accurate. For myself, well, it’s a different story. I do things backwards — you tell me the due date you want, and I’ll cut the scope accordingly. It will work and solve the problem! Just not in the way you expected.

@spongegeoff I wish it was legal to kill my mother as it’s legal to kill hamsters…

@cprn man… quite unrelated, and I feel like a weirdo, but I can’t help but read your nickname as “C porn”. Are you by any chance a C programmer?

Depends on the application. Sometimes it’s better to return a default value/approximation if the function will be called a lot, and the results don’t always have to be precise. If you rarely call this function, and you always care about the result, you should throw an error.

“But then, part of me can think of a very simple way to prevent that from happening again: the Rust project as a whole needs to be better, and communicate better.”

Yeah, no shit 🤷‍♀️

“If your codebase is bad, you just have to write better code.”
I guess if my performance as a programmer is bad because of depression, I must just stop being lazy.

@Sid2006 I’m sorry, okay? I’m bad with words, I’m autistic, and English is my second language. I didn’t mean to tell you were less fortunate in that comment of mine

amazing!

@PaperTrail omg! Did you try a mosin nagant? If so, what’s your opinion on it?

@Oktokolo I mean I know how to load it. You just hold the bolt handle with the palm of your right hand, as hickok45 had shown. But bruh, just imagine a garand with a fucking forward assist. That’s ridiculous

@vintprox wym not html?

@Demolishun thank you 🙏 I missed this beautiful message somehow. I’m here to undo the injustice.

Better even, use system font stack instead of this custom font.

https://systemfontstack.com/

You forgot the appropriate font fallbacks! In iOS lockdown mode where custom fonts don’t load, or in any other case they didn’t load, users will see times new roman. But you’re clearly using a sans serif typeface. It means you should do a fallback, like this:

font-family: “(your custom font)”, sans-serif;

If your font doesn’t load, it will fall back to a generic sans serif typeface, preserving your design intention.

Do you want to? If so, you’re already not a true nihilist.

@Sid2006 sorry. I didn’t mean to call _you_ less fortunate. I meant other people that have to work with bad managers/terrible outsource companies, which frankly is a majority, even among devRant audience. The only reason I don’t have to deal with this BS is sheer luck, not skills.

@Sid2006 I follow college standards. I know why they are important, and the trust I build is always enough to convince them to follow me. I don't work without trust. About managers: I don't see them. I don't believe they are important. To me, they don't exist. This is why we don't hire them.

I work with the business directly. I only care about the business and the users. If they insist this structure should be revisited, they don't understand my job and sabotage it. I don't tolerate this behavior.

However, I can empathize with people less fortunate than myself. But please, don't discredit college standards just because some managers manipulate people into doing it.

@Sid2006

1. Responses with error codes can contain bodies that clarify the error. Also, if the API didn't work as in your example, a 5XX code should be returned.

2. If a frontend dev can “just” write one handler, then a backend dev can also “just” return correct codes. It's not about toast messages. Fundamental things like API response codes mechanism should be defined very early on. They rarely change later. I don't want to subject every frontend dev that joins us in the future to “well, we don't follow REST here, write a handler”. There can also be multiple frontends — internal UIs, admin panels, mobile apps. Why should all of these devs cover up the backend team's incompetence?

3. See 2. Also, why enforce incorrect “standards”? Every framework in existence can return correct codes. You should go out of your way to break it.

4. Translation: “it's nothing major, we'll fix it later”. Why have this philosophy on new projects?