Any Tesla or Space X workers want to weigh in here, can't feel good to be under the pump 24/7 while your CEO has spent most of his time since November arguing with everyone online.
Unrelated to anything, but we might as well get something useful out of this thread - for all the SpaceX-ers, is Mars actually a thing or just an abstract concept that no one is really working on?
Seems a valid use of resources if you have a way to vaguely associate it to some academic side-project, just don't start monetizing the output and beware the wrath of stressed out PhDs if you use too much capacity.
I got a rental raise for a 1 bedroom in Bushwick from $2700 to $3500.
I told them this was unreasonable for the area, but they refused to budge on the price, offering a paltry $50 discount.
That apartment eventually got re-rented for $2700 according to StreetEasy as they couldn't find tenants at the price point they (or the "algorithm") wanted.
Many people are willing to pay more to not move, especially if they're in a walk up. Forcing returning tenants to pay more seems like one of the first moves landlords would try.
Sounds very similar to my early 2020 - mid 2022. Got a "dream role" at Apple that utilized my niche expertise, was assigned to a high-value component of a high-impact project that sounded like a perfect fit.
2022 comes around and we have a barely functional prototype that was initially due to be shipped in mid 2021, constant turn-over in software engineering and product management, the front-end that had been build didn't align with the back-end due to a complete lack of project coordination, but felt tied to the role due to stock grants.
Left to join a 4-person start-up founded by one of my good friends from college and haven't looked back since :)
What sort of pedantic geek with a grudge do you have to be to think you're making some sort of point by stating the absolutely irrelevant fact that 20 years ago there was a crappy abandoned PHP project that was initially used by an ambitious teenager as a starting point to create the world's most successful publishing platform and one of the top open source projects of all time?
Seriously, what do you think your point is? That the past 20 years of WordPress success is somehow the result of some nefarious teen fraud back in 2003? That Matt shouldn't get credit for creating WordPress because he started with a few hundred lines of PHP from an - again abandoned - open source project?
The bitterness and stupidity on the Internet will never cease to amaze me.
Hi, developer of b2 here. Can't believe I finally have to create an account on HN, but here we are.
First of all, Matt and Mike (along with Doug, Alex, Donncha, and other devs from that time) deserve all the credit for WordPress and its success. Often I get way too much credit from friends and people who mean well.
I have mixed feelings about calling b2 a crappy project though.
When I started writing it, I only had one month of PHP behind me, and no computer science background.
It was a time when Blogger was flaky and a lot of bloggers were tired of the frequent downtime. There was a demand for blogware that could be installed and customized easily, and most existing blogware fell short (those written in Perl required specific hosting, others were not easy to use or customize).
What I brought with b2 at the time wasn't technical prowess, but software that could be installed on super cheap webhosting plans by just editing a config file and uploading.
I take pride in the documentation that allowed folks who only knew HTML to customize their blog's markup without having to know PHP or a custom template language. (Keep in mind we're talking about a time when bloggers would hand-write their site's HTML, ready-made themes weren't a thing.)
I have fond memories of the dozens of fine people who contributed ideas and code to the project; among those contributions were the first opensource implementation of PingBack and perhaps the first of TrackBack too (not so sure about that one, but at the time there wasn't a lot of GPL blogware).
The relative success of b2 (among those who self-installed their blog) was not due to the intrinsic quality of its code, but to those important things. It was mostly crappy PHP, but there is more to projects than just code.
I would keep on talking about what blogs looked like in 2001, but if I recognize your name correctly, I believe you were there too.
Finally, yes, it was abandoned. I was suffering from depression following the loss of my job at the time, and took time away from the internet. It was just not physically possible to open a code editor, or even reply to email, for a few months. It's not like I decided that I had enough and decided to explore greener pastures. If I could go back in time, I would hang on to the community we had, instead of abandoning the users and contributors.
TL;DR: Matt, Mike, and the team deserve all the credit for WordPress's success, and it's a bit harsh to judge a 20+ years old project created by an enthusiastic newbie coder.
I deeply apologize for calling it crappy - that had absolutely nothing to do with my point and not based on any sort of knowledge beyond dim, decades old memory, and also more based on how I describe "solve a problem" coding. Literally ALL my code is crappy, if that helps clarify. Really, I'm totally sorry I threw that in there, I could have made my point without it.
Worse, someone else might read my comment and worry about publishing their own project which is the last thing I want to do. I used to worry constantly about the quality of my projects. I don't any more because I realized that a line of published ugly code which solves a problem is worth thousands of perfect lines of code which never sees the light of day, and that open code can be used as a starting point for others. That's exact what happened with b2, of which you should justifiably be proud and happy!
upvoting to at least justify your effort in creating an account here :)
Fond memories myself - of finding, downloading, running B2 back in 2002, then wondering "what happened to Michel V?" - then moving on to .72 of Matt/Mike's fork...
Thanks for rounding out the missing details, and for your understated contribution.
"WordPress" didn't acquire Tumblr. Automattic did. Automattic (A8C) is the corporate entity behind WordPress.com and Tumblr.
The open source software can be found at WordPress.ORG and while the CEO of A8C does sit at the head of the board of the OSS project, his reach extends as far as others are willing to implement his ideas. Also to be fair, he does pay plenty of A8C employees to "contribute" to the OSS project on company time. This is largely how the Gutenberg project was pushed over the finish line.
It could work, but the moment FTX started allowing FTT to be put down as collateral on multi-hundred million dollar liabilities, the entire house of cards fell apart.
I asked an adjacent question and am also curious, great that they have provided another option for the OpenJDK community but I can’t see anything compelling that would make me consider this over Adopt.
If you are already paying AWS for premium support, one reason to use Corretto rather than Adoptium is that your AWS premium support plan covers Corretto as well.
"If you already have an AWS Support Plan, Corretto is covered on the same basis as all other supported AWS Services and software." https://aws.amazon.com/corretto/faqs/
Could someone provide a TL;DR on the major patches/benefits that Corretto has over Adopt or other community driven JDK implementations? It is unclear from the documentation but I am assume they have some secret sauce for faster boot for their Firecracker VM instances.
Adoptium is not "community driven" (it's made by IBM), and there is only one OpenJDK implementation, the one led and primarily developed by Oracle, with contributions from other companies. What Amazon or IBM do is build the source and distribute the binaries (look at the licence).
"...Eclipse Adoptium, built by IBM, which is the only distribution built by a team that isn't involved with the OpenJDK project, isn't very familiar with it, and isn't a member of the OpenJDK Vulnerability team, and so get security patches only after the other vendors have delivered their builds. "
My understanding is that ties between the Eclipse Foundation and IBM are loose enough by now to not call this project an IBM thing. Eclipse did originate at IBM, but that was close to 20 years ago.
That may be so, but >90% of the work on this particular Eclipse project is done by IBM. Just as many companies contribute to OpenJDK but it is primarily an Oracle project, and Oracle does most of the work, Adoptium is an IBM project. That, in itself is not good or bad (although it is somewhat bad because, unlike other JDK distributors, IBM is barely involved with OpenJDK and the IBM team that makes the Adoptium builds is not particularly familiar with OpenJDK), but it is certainly not a "community led" distribution -- it is, de facto, an IBM-led one. It did not start out this way, but it has been this way for several years now (they did the same with https://en.wikipedia.org/wiki/Apache_Harmony).
Are we talking about the (Open)J9 flavor here? It was featured more prominently on the AdoptOpenJDK page, but has now all but disappeared on the Adoptium site. J9 is something that I can definitely associate with IBM, what I'm having a hard time with is connecting the work on HotSpot builds to the company.
I'm talking about the Adoptium (née AdoptOpenJDK) builds, which are made by IBM. IBM aren't involved much with OpenJDK, but they can still run `make` on server farms. Although Eclipse OpenJ9 is yet another IBM project.
I worked at AWS and Corretto came out towards the end of my tenure there. At the time (Java 8), it included in house patches that upstream haven’t or due to politics refused to adopt.
Now that I don’t work at Amazon any more I still advocate for the distribution for the LTS model, and the fact that it contains fixes that are only discovered when running in production at the scale of Amazon and AWS.
Which has been a staple of long-term JVM production guys for a long time. You can use their releases free of licensing but can get commercial support if/when you need it.
You probably shouldn’t. Last I checked the OpenJdk docker images use the Debian builds of OpenJdk and there’s been multiple times where they’ve shipped vulnerable builds. [0] You should probably just use the Zulu builds.
Wow, that's awesome - 8 had a handful of custom patches and some backports, 11 had only backports, and 17 has nothing. This is kind of the best possible story for a distribution fork!
