alien_

This is unfortunate and will cause a lot of migration work, and it was poorly communicated so I can understand the frustration but I'm thankful to Travis CI for their past services.

My project only needs about 30m of build time monthly and the migration to something else may cost me a few hours of work. At my hourly rate that may be significant enough, so for a while I would rather pay a small monthly fee to cover my limited needs.

As per Wikipedia the overdose threshold for adults can be up to 50k/day https://en.wikipedia.org/wiki/Vitamin_D#Excess

As an anecdote, about half a year ago my sister-in-law's 4 year old found some vitamin D pills and ingested what was left in the pack, in total around 60k IU, hours before anyone noticed.

The doctor said to just avoid giving him any other Vitamin D for the next few months and it should have no consequences.

Luckily it was just Vitamin D, pretty much any other pills she had would have probably been deadly at such a high dose.

I did a similar move last year when I changed the license of my AutoSpotting project to OSL-3, after my MIT code was taken by two startups that built products using it without contributing anything to the development efforts.

FOSS is a Commons, in my opinion every organization, government and company should use it as much as possible and invest in it a fraction of their IT budget, even if just 1%.

This would add up to resolve the current FOSS funding problems and the FOSS ecosystem would thrive.

They could do it by hiring developers or FOSS companies and/or funding targeted to the projects they use with a subscription like Tidelift.

Operating mode sounds much like it happened with Jamal Khashoggi, could he be another victim of MBS or some other Saudi prince?

Thanks!

My former employer is still using it and saving yearly multiple times my previous 6 digit salary, so I got a nice promotion out of it before I left.

It also helped me get my current job at AWS(pretty much half of the interview I was just talking about how I built it), and I now make some $500 monthly (before tax) from a few users who pay for official binaries.

I'm now only working on it occasionally, just enough to maintain this income stream, but previously I put a lot of time and effort into building it.

My motivation to work on it plummeted when I saw those companies reap the benefits of my hard work without giving anything back.

As author of an open source tool that was already steatlh-forked twice without any contact whatsoever by VC-backed startups - including clearly copying text from my website/FAQ - without giving any sort of credit on the idea/implementation they used for 80% of their product but on the contrary claiming how revolutionary their products are and best idea since sliced bread, and even not satisfying the basic MIT license terms, I can completely understand your frustration.

At least they were nice enough to pay you a trip to Seattle and (briefly) mentioned your project in the release announcement, I didn't even get a "thank you".

As a result of this I re-licensed my code from MIT to OSL-3 and reduced my involvement in this project a lot so I focus on the things that actually matter in life: my wellbeing and spending the time with my family.

There's a quote that states that all models are wrong, some happen to be useful.

With this in mind I think we should stop nitpicking on non-specialists who try to raise awareness of this pandemic.

Yes there might be some differences from what a specialist would have done.

Due to the speed at which the situation evolves and the inability to test everyone daily there are lots of unknowns so even a specialist may not be able to give a more much precise figure, everything is going to be a rough estimate.

This is a very serious situation and it's better to err on the caution side, people's lives depend on everyone doing their part.

Non-constructive criticism of people who raise awareness will erode people's buy-in and people will die because of this.

I expect that the number of people who die monthly for a certain condition to be relatively stable over time.

We can compare the usual number of people who die of pneumonia with the current one, and any significant difference can be attributed to this novel virus.

Thanks for the shout-out, really appreciate it.

If you don't mind I'd like to get some feedback/feature ideas from users like you.

Please get in touch with me on https://gitter.im/cristim

It's easy to raise the billions required to fight this. It's peanuts for governments and even larger companies hoarding tens of billions that have a lot to lose because of such pandemics.

Have a look at https://github.com/AutoSpotting/AutoSpotting or the FAQ section on https://autospotting.org

If those don't answer your questions feel free to reach out to me and I'll do my best to explain further.

The author of AutoSpotting here, this is often being asked and I'm happy to clarify it.

The mixed capacity ASGs currently run at decreased capacity when failing to launch spot instances. AutoSpotting will automatically failover to on-demand capacity when spot capacity is lost and back to spot once it can launch it again.

Another useful feature is that it most often requires no configuration of older on-demand ASGs, because it can just take them over and replace their nodes with compatible spot instances.

This makes it very popular for people who run legacy infrastructure that can't be tampered with for whatever reasons, as well as for large-scale rollouts on hundreds of accounts. Someone recently deployed it on infrastructure still running on EC2 Classic started in 2008 or so that wasn't touched for years.

Another large company deployed it with the default opt-in configuration against hundreds of AWS accounts owned by as many teams, many with legacy instances running for years. It would normally take them years to coordinate as a mass migration but it just took them a couple of months to migrate to spot. The teams could opt-in and try it out on their application or opt-out known sensitive workloads. A few weeks later then they centrally switched the configuration to opt-out mode, converting most of their infrastructure to spot literally overnight and saving lots of money with very little configuration effort and very few disruption to the teams.

If you want to learn more about it have a look at our FAQ at https://autospotting.org/faq/index.html

It's also the most prominent open source tool in this space. Most competition consists of closed-source, commercial (and often quite expensive) tools so if you're currently having any issues or missing functionality, anyone skilled enough can submit a fix or improvement pull request.

The AutoSpotting author here, always feels great to see my little pet project mentioned by happy users. Thank you for making my day!

To set matters straight, AutoSpotting pre-dates the new AutoScaling mixed instance types functionality by a couple of years and it (intentionally) doesn't make use of it under the hood for reliability reasons related to failover to on-demand. To avoid any race conditions, AutoSpotting currently ignores any groups configured with mixed instances policy.

In the default configuration AutoSpotting implements a lazy/best-effort on-demand->spot replacement logic with built-in failover to on demand and to different spot instance types. To keep costs down, it is only triggered when failing to launch new spot instances (for whatever reason, including insufficient spot capacity).

What we do is iterating in increasing order of the spot price until successfully launching a compatible spot instance (roughly at least as large as the original from CPU/Memory/disk perspective but cheaper per hour). If all compatible spot instances fail to launch, the group keeps running the existing on-demand capacity. We retry this every few minutes until we eventually succeed.

There's currently no failover to multiple on-demand instance types (this is a known limitation), but this could be implemented with reasonable effort.

We're also working in significantly improving the current replacement logic to address a bunch of edge cases with a significant architectural change(making use of instance launch events). I'm very excited about this improvement and looking forward to having this land, hopefully within a few weeks.

At the end of the day, unlike most tools in this space(including AWS offerings) AutoSpotting is an open source project so if anyone is interested in helping out implement any of these improvements(or maybe others), while at the same time getting experience with Go and using the AWS APIs, which are nowadays very valuable skills, you're more than welcome to join the fun.

Thank you for the encouraging words, I'll try to make the distinction more clear.

Initially I thought to use sidekiq as an example, they run only on an .org but indeed seem to have better separation between their OSS and commercial bits.

From https://AutoSpotting.org, a software that I wrote a few years ago and I still maintain and work on occasionally I earn about $450 monthly.

I also have a bunch of shares and funds that increased by some $4000 over the last year.

I tried this for a while but it decreased user adoption a lot so I added it back but with a savings limit of $1000/month.

Looks like most people don't seem to want to build it from source and it deters them to use it if I don't provide easy to install binaries.

It also also impacted negatively the conversions to paid users, people who convert seem to try the free binaries first and update to the paid version if they need to get above the $1000 monthly savings limit or they want the peace of mind to be on stable builds. I then charge them $29 monthly for the stable and unlocked version that I have also tested.

I also experimented with various pricing tiers and decided to settle to this for simplicity.

I don't have much to complain about the usability of the software, but they are making hardware that should not be made.

I'm the unfortunate user of a MacBook Pro company laptop with 8GB RAM and just two USB-C ports.

This sort of hardware should not be made anymore. The memory is insufficient (my laptop is always paging) and the USB-C is forcing me to always carry a dongle, not to mention that just two is not enough considering that one of them is used for the power cable.

It really feels like the people who designed this laptop never actually had to use it.

I wish they would be forced to use it for a while to get a feeling of how crappy it is, so they stop making such terrible hardware anymore.

At Amazon, perhaps one of the largest and most successful employers, the solution to this is that when interviewing, everyone's main goal is to hire people better than the current average of the team.

To ensure this, someone experienced with interviewing from outside the team/organization, so called bar raiser, is always added to the interviewing team. This person is there to ensure high quality hires and has hiring veto power.

The rest of the interviewers are from within the team, likely under pressure to compromise on quality when they're desperate enough to hire someone, but they can't do it unless the bar raiser agreed.

Likely all they need to do is run Word for typing and printing text documents. This worked perfectly fine with Windows95.

I've recently switched jobs and got a Mac work computer after using Ubuntu for more than a decade.

I like some things but I am also frustrated with a number of things: I miss the split clipboard, I hate the insufficient number of USB ports and the fact that I have to use a dongle, I miss the vertical maximize and the touchscreen.

It's already there, I've often seen console output with translated error messages. Helpful for the users but not of much use to developers, unless using error codes as well

This is a matter of billing, if Lambda charged per millisecond instead of the current model of 100ms chunks, this wouldn't be an issue.

At scale/high performance there's a lot of waste with the current pricing model.

Better not to sell than to repeat the fate of Wunderlist, the founders wanted to buy it back to avoid the shutdown.

A better way than tagging is to give each team an AWS account to maintain and pay from their own budget.

The Webkit/Blink engine is far from being single vendor, they are vibrant open source projects with many companies that contribute to the development efforts, pretty much all browsers except for Firefox will be based on it soon.

Web developers would rather have a single good engine, assuming that it's good enough and continuously developed.

IE failed back when they all but ceased development for a number of years and since it was closed source nobody could take it over.

Yes but the military industrial complex that likely lobbied for this would have huge profits if a new arms race starts.

Yes, that's why you should incorporate it in your morning routine right right after waking up, while still wearing the pajamas and then take a shower.

That's actually a great idea, thanks for sharing it!

I'll try to make it paid from the mobile phone.