nofunsir

I read every single one. Any app that does this gets uninstalled and a nasty letter to software managers.

Don't underestimate the effort a software developer will put forth to create mountains of complicated automation and scripts if it allows them to be lazy. And they see no issue with this. So why would they see an issue being accountable for yet another agile cycle.

Rev number go up!

This should be illegal if auto-updates are enabled or eventual updates are forced. Not joking.

Nowhere else in society do we allow such self-serving laziness and unethical negligence (looking at you, purposely destroying backwards compatibility of APIs) at a professional level. Most other professions have steep legal consequences if they hide their actions or inactions.

Still not convinced it's not a honeypot. Would like to see concrete evidence.

I used, administered, setup, and customized many on prem gitlab instances for years. I gitlab doesn't memory leak, you're making that up. It's exactly as resource intensive as the number of resources you setup. Can't say the same for JIRA et al.

This comment makes me suspect this entire thread as some astroturfing for that other product.

I don't think this is productive, since you're so adamant [1] that "big C memory safe programs don't exist." I know for a fact they do. Most of the software you won't ever see. What do you think powers the most critical sytems in, say a fifth gen fighter, or the software that NSA relies on in their routers?

I'll give you a hint. It's neither rust- nor scrum-based. I'd rather change careers or retire than work another day doing scrum standups.

[1] https://news.ycombinator.com/item?id=45353150

Not nonsense. Don't be reductive.

I've got a bridge to sell. It's made from watered-down concrete and comes with blueprints written on site. It was very important to get the implementation started asap to shorten the review cycle.

Unit tests does not make Software Engineering. That's simply part of the development phase, which should be the smallest phase out of all the phases involved in REAL Software Engineering, which is rarely even done these days, outside of DO-178 (et al) monotony. The entire private-to-public industry has even polluted upper management in defense software engineering into accepting SCRUM as somehow more desirable than the ability to effectively plan your requirements and execute without deviation. Yes it's possible, and yes it's even plausible. SWE laziness turns Engineers into developers. Running some auto-documentation script or a generic non-official block diagram is not the same as a Civil PE creating blueprints for a house, let alone a mile long bridge or skyscraper.

I see Gianluca Martino let arduino.com lapse/is squatting it. Maybe the experiment is done? Is Adafruit no longer #TeamArduinoCC ?

Tangentially related. Youtube web is now, as of the last month, strictly enforcing "referrer header" for embedded videos. Even if you spoof it, it doesn't always work. You can't navigate directly to "youtube.com/embed/<videoid>" to watch something without giving google some direct information.

Since when are public-facing error codes just lies?

"Oh Error 15 something went wrong, tee hee." "Oh Error 153 better try again, (got em, guys!)"

They operated for a while, before finally updating their FAQ stating this is intentional.[1]

[1] https://support.google.com/youtube/answer/171780?hl=en#zippy... " Provide a HTTP Referer header to enable video playback

Our Terms of Service require embedders to provide a HTTP Referer. If this information is missing, viewers attempting to watch embedded YouTube videos will encounter blocked playback and an error screen (“error 153”). These viewers will still be able to click “Watch on YouTube” to view the video on YouTube. Note that directly accessing the embedded player without an enclosing webpage or context (such as accessing it from your web browser's address bar) will typically not have a HTTP Referer and users will encounter the error screen; the embedded player is only intended to be used within an embedded context."

are rust devs the new vegans?

>AI training is fair use.

You say that so confidently as if it's not the subject of a heated controversial debate this very moment.

>people who are completely computer illiterate, but need to use a computer for work/school etc and have no desire to learn the basics of using a desktop OS.

basically gen zalpha.

Nope. I know a couple were on macrumors forums. And to be clear, there were suspicions of Apple slowing down devices to get you to upgrade far before Batterygate. It used to be painfully obvious, but with apple's protections it wasn't knowable.

Before the whole "batterygate" thing[1], there were forums and discussions on macrumors and similar inquiring about the feasibility of inserting no-op codes deep below the kernel that would kick in under certain conditions. Post-batterygate, you can't find anything NOT about batterygate when searching.

1] Which I still firmly believe WAS indeed a power-supply design failure that would have forced a massive hardware recall had they not done something (slowing down the os). I believe it encompassed everything from inaccurate CPU power estimates to something actually incorrect with the PCB design, causing brown outs - and not merely a battery-aging red herring as is the reported scandalous reason they were "caught". In fact, I think Apple is GLAD that all it amounted to was some philosophical hullabaloo about protecting your poor aging battery.

To clarify, I suspect the "aging battery" merely exposed the real issue - the incorrect PS design - which Apple successfully covered up.

Shhh - they'll hear you!

Surely it will be deleted as soon as some manager remembers it exists.

I just want normal buttons and dials back. Not time-based capacitance buttons that take 5.02 seconds to activate, not 5.0 seconds; nor free-spinning encoder wheels that mandate you give it a jiggle before the washer does anything, even if it's already on the setting you want.

I want kachunk-a-chunk back first. Then we can decide if it needs smarts.

Website owner has disallowed Wayback Machine.

To add, it's really satisfying to build your own, push it and host it on your own internal repo that anyone in your group can use.

"Just go get the DEV image, Josh."

Wait... this whole time reading this thread, I'm racking my brain for what bitnami provided (I used to use them before docker came around. I never would have got Redmine up and going without them -- the install seemed so foreign.) that building a docker image couldn't, because surely everyone knows how to build one from scratch, right?... right?

Is all the panic because everyone is trying to avoid learning how to actually install the pieces of software (once), and their magic (free) black boxes are going away?

I recommend VS Code remote connections and docker builds via the docker extension to do rapid build-run-redo. Remember to make sure it works from scratch each time. You can automate them with Jenkins... (which came first, the Jenkins or the Jenkins Docker image?) I also recommend Platform One. (you'll need a smart card) I also recommend reading the particular software's documentation ;)

I personally sent several scathing emails directly to directors about the issue. I have a long iMessage history and there was a point that just entering a single character in the search field would lock up my mac, let alone my older iPhone.

I have noticed and appreciate the change, so my headcanon is that they actually do read feedback. ¯\_(ツ)_/¯

I still go to File looking for File > Preferences and File > Quit.

No, ads aren't the solution for everything, and in my opinion anything.

It appears they are returning a 403 if you don't allow any cookies.

When Apple first launched face ID, there was talk (I can't remember where) of developers being excited about the possibility of tracking where their users were looking.

Ironically, they'd try to get you ... or someone... anyone! on fraud. Can you imagine the same argument made in the example of getting up and going to the kitchen?

> Your honor, they agreed to our terms and conditions which stipulate you MUST stay in the recliner facing forward the whole time. By getting up to <do something important and not waste their life watching ads>, they've defrauded our advertisers! We demand to be repaid in the form of 43 lazyboy hours per year.

No it's not. It's shining a light on where the real WWW goalposts are and always have been.

The pedantry comes not from someone using their User Agent however they want to use it. It comes from a company trying to (with receipts and lawsuits to prove it) LITERALLY redefine the World Wide Web into their own money making machine, and punish anyone who rocks their boat. They can cry "legal argument" all they want. At the end of the day, they're trying to force pedantry on their users. The only problem is most of the public has bought it Hook, Line and Sinker.

>I can view it under any terms I chose until they find a way to exclude me without excluding all the attention that being on the public Web gives them.

This is the unsung argument everyone forgets! It goes to the very start of why someone might register a domain name and set up a website on the... World Wide Web... for people to visit with their User Agent software, ask for some HTML and get some HTML back. "HOW DARE YOU NOT DO A RANDOM SOCIALLY DEFINED THING AFTER ASKING FOR OUR HTML (AND OTHERS' MP4S)?"