rty32

That's a very arrogant attitude.

I'll give you one example: I sometimes can't open OpenAI API documentation due to some stupid Cloudflare captcha checks. No, on Firefox, however many times I click that checkbox, I can't go through the verification, just to read some static content. Not even if I disable adblock and tracking protection.

I don't even see a checkbox at all on Chrome or Edge.

Yes until it fails

https://www.theverge.com/2023/11/27/23978591/google-drive-de...

It is absolutely not common.

It is reasonable to expect contributors to have a certain amount of programming experience, but I rarely see any open source projects ask for requirements in a very specific area like a job posting. Many open source projects -- I am not talking about React or VSCode -- would be happy to see people creating pull requests at all, and are willing to provide pointers or hints for people who have experience but may not be so proficient in a specific language. Most of the projects work well that way.

They can do all of that, of course. My point is that their condescending attitude is going to lose potential contributors like me, when most open source projects embrace a much more welcoming environment. Maybe they are doing fine, I don't know. But I have worked on enough open source projects to know that it is not the best position they can be in.

I find parent's comment very truthful and (mostly) reflects the reality, based on my personal experience. Saying that as someone who created many pull requests and opened/participated in many github issues for open source projects.

To be honest, I think it is true. They declared "issue bankruptcy" in one of they repo:

https://github.com/microsoft/TypeScript-Website/issues/2804

Contrary to many people's perception, Microsoft is one of the biggest contributors to open source, whether for projects they "own" like TypeScript or VSCode, or other common projects like Linux. The amount of users and bugs/feature requests etc don't match headcounts available at Microsoft.

Not 100% agree but would almost say the same thing.

As someone who made small contributions to several projects and left comments under many GitHub issues, things that I see:

* Heavy users are more likely to report bugs and end up contributing to the project * If many people run into the same issue, more likely someone will create among them will write a fix, or at least suggest a workaround * A "healthy" project -- one that addresses GitHub issues and pull requests quickly, that responds to people's questions instead of ignoring them, that encourages technical discussions, is more likely to attract even more contributions. * Some projects have issues and pull requests that are open for a long time without any response from maintainers (despite active development). I myself wouldn't even bother reporting a bug because it's not worth it

Meanwhile, even under this thread, you can find people that expect certain amount of experience with a particular language. That just says to me they don't want contribution. Why? I am no expert in that certain language, but I am experienced enough in software engineering that I can jump into many codebases and create a high quality patch with some ChatGPT. I've done this many times before. If they are so obnoxious I'd rather put my energy elsewhere.

I checked the time to make sure today is in the year of 2024.

I swear this has been widely known at least since the Win 98 era.

In theory, yes, but in practice, people who know how to compile gdb is a small subset of people who need to debug c code.

Not to mention that it actually takes extra time to do so, when people are used to debug Python/JavaScript/Go code with one single click these days.

No, part of the malicious code is in test data file, and the modified m4 file is not in the git repo. The package signed and published by Jia Tan is not reproducible from the source and intentionally done that way.

You might want to revisit the script of xz backdoor.

Not going to happen in the US for the next few years, at least.

Jeff Bezos killed the endorsement because he wanted Trump to win. Trump will return the favor.

One thing I find people don't talk enough about is how bad AWS documentation is, across the services. They contain outdated information about services, inconsistencies for the same feature, and lack explanation and meaningful examples to help you understand how things work and work together, even for common workflows. Example: try to make Sagemaker use EMR for Spark analysis, as a beginner who has little idea what IAM is and how to grant permissions for different services. It will be fun.

I am just amazed that people are able to navigate the services and configure them properly.

Such cases would be pursued by DOJ or FCC or some other federal agency that the President has 100% control over. If the president asks to drop the case, it will be dropped.

Wild take that might actually be true: by attacking the Biden administration, the company wants to appeal to Trump and maybe even get Trump's attention (and favor), hoping that the Trump administration will loosen the regulations on betting and eventually make it legal to operate their business in the US.

The CEO or the company can only be in trouble if they are found guilty in court. That's not going to happen in the next two months, and Trump probably couldn't care less about this.

Well, I wouldn't consider 7700 low-power in any sense, maybe 7640U or 7840U on a mini PC. You are running Linux the entire time?

A few x86 CPUs used are 4-7 generations old. Not sure what to make of that.

Yeah. I scratch my head when there is a ton of new models and competition happening in the mini PC market that provides good value for end users, but nobody notices. When Apple releases a new mini PC, suddenly it's like a breakthrough or something. I even see people say "the entry 8 core Ryzen you can get on a desktop PC is 7700" when discussing this new Mac mini on tech forum, as if giant towers are the only kind of desktop PCs and 7840U/7840H(S) doesn't exist. (You would expect these people to know better)

I guess marketing matters.

Eh, how does using a VPN make it easier to MITM attack yourself and modify the response of that GET request?

At Amazon, if you don't get promoted, you get pipped, eventually.

> In the first ad, Apple Intelligence enables a goof-off who wastes time and annoys his colleagues to surprise his boss with an unexpectedly well-written email. It’s not clear that the boss is impressed; he just can’t believe the guy would have written a professional message.

This feels... weird. If the ad was released early 2023, it would still be relevant. But hey, we are now at Nov 2024, exactly after two years after ChatGPT was released. Anyone who has been half paying attention to "AI" wouldn't be impressed any more with a formal, professionally written email from anybody. Saying that as someone whose performance review had evidence of being "enhanced" with ChatGPT but didn't find it surprising.

Well, what's more weird is the setup itself. Do bosses expect to read this kind of super formal email from their direct reports? Do people actually write first versions of emails like that? Something is off here. At least I don't think it ever occurred to me that I need to "rewrite an email to my boss using a professional tone" to my direct boss.

Good points. I was more focused on the technical side.

I want to add a bit more to "easier deployment" -- traditional model is that you push updates at some interval (regular interval like semi annually/annually or non regular intervals), and you need to manage multiple versions and potentially patch multiple versions for severe bugs or security issues. Lots of software still works that way. But with office 365, jira etc you only have one version to worry about. Of course it means different risk levels, SLAs etc, but that's a different topic.

> I never fully understood why this programming paradigm died off

My two cents --

A few reasons (briefly, I could have talked a lot more)

* Shift in platform: Windows is no longer the sole platform people want to build their apps for. Not a bad strategy by itself, and lots of companies still only develop for Windows (e.g. specialized software for instrument control etc), but people increasingly want their stuff to work on iPad, Chromebook etc and maybe even phones

* Shift in screen size: It used to be that everyone runs Windows on a 800x600 screen. That changed, and then changed quickly. Many different resolutions and screen sizes. The drag and drop thing just doesn't work well for that. The web model, where you write "responsive CSS" and the browser handles the rest for you, works better.

* Software and their UI got a lot more complex and require more expertise. On the other hand commercial software becomes easily available and accessible for those purposes. For the examples you mentioned -- stock control system, sales tool, they may be fine with VB6 for a prototype but can quickly get complex. And there is likely a commercial software you can buy and download within a few minutes at an affordable price.

* Shift to online/cloud: vast majority of "small VB6 applications" were used locally, and they never connect to the Internet. That's different now.

* Shift in language: BASIC/VB was often used for teaching, and it is indeed great as a first language to learn. Although Python already existed at that time, it became very popular, and I think many people would agree Python is a much better language than BASIC, in many ways. As a result, BASIC along with VB went out of fashion.

Dumb question: how is this better than connecting the digital piano to a DAW on a computer? Is that the "set and forget" aspect of this device?

What about using a relay as a temporary solution to remotely turn it off instead of physically yanking the cable?

Maybe that's good enough for them, people never touch this problem again, and we wouldn't have this story (which of course would be sad). But it occurs to me that the author wasn't in a rush to fix this and had plenty of time to poke around. I wish I could do that.

I'd like some references of "Java mindshare is going down fast".

Sure, lots of new project/code uses languages like Go these days. But Java is still very dominant, especially at companies like Amazon. It currently sits ar #3 on TIOBE.

Curious -- how many people are writing Rust in your company?

Nice! And glad to see it's MIT licensed.

I wonder if it is feasible to use this as a replacement for p2k, instapaper etc for the purpose of reading on Kindle. One annoyance with these services is that the rendering is way off -- h elements not showing up as headers, elements missing randomly, source code incorrectly rendered in 10 different ways. Some are better than others, but generally they are disappointing. (Yet they expect you to pay a subscription fee.) If this is an actively maintained project that welcomes contribution, I could test it out with various articles and report/fix issues. Although I wonder how much work there will be for handling edge cases of all the websites out there.

That's exactly why I have been de-Googling for the past year. I have lost all trust in Google. I still use some of their products, but I make sure I never got in a situation where losing my Google account means losing important data or getting myself into serious trouble.