It seems everyone loves creating packages and releasing them as open-source. I understand the appeal, it’s much easier to release something this way as it lets you wash your hands of a lot of the responsibility.
Need a bug fixed, send a PR or GTFO. Have some questions about how to do something, hopefully, Stack Overflow can help you.
Of course, this is merely a caricature of some maintainers, and then you have others that are super responsive and are happy to help you use their package.
If you are one of the second groups that are responsive to support and community engagement then I’d love for more of you to consider making future packages commercial. Granted it’s probably not going to be as easy as just pushing up a repo, but we have tools available now like gitstore that makes this easier than ever before.
It seems many developers are making the switch to TablePlus because it supports a wide range of different database types, has an active development team, and is a stable app.
I started using it yesterday and I’ve been fairly impressed, plus they are working on an iOS version which I’m super excited about. If you are using it on a Mac here is a cool Alfred workflow by Chris Renga for opening a database quickly.
AgileBits just released 1Password 7 for the Mac and it comes with a ton of new improvements. Some of the things I’m really looking forward to is the new design and the ability for better app integration:
With our new app integration we’ll automatically suggest logins for the current app you’re using. Along with support for drag and drop, this is a real game changer.
Not being able to use 1Password for standalone apps is one of the reasons I’ve always preferred browser-based apps. So I think this alone will be huge.
If you are not using 1Password or another password management system then I highly recommend you start and you couldn’t go wrong with 1Pass. It’s seriously great and when you hook it up with 2fa logging in has never been quicker and easier.
The next Ulysses version will ship with greatly improved code blocks.
You’ll have to mark up the beginning of a code block only once to let it span as many paragraphs as needed. No more backtick fatigue! Also, we revamped the appearance of code blocks in the editor to make them easier to distinguish from the body text: they’re set in a monospaced typeface (what else would make sense for a code block?) on a colored background (depends on theme). What’s more, the new code blocks will import from, and export to GitHub-style fenced code blocks. Oh, and you’ll be able to use them in external folders as well. Yay!
I really like Ulysses, but code blocks are the number one reason I stopped using the app. The current system is clunky and annoying so I have a lot of high hopes for this change. It does worry me how this is described and I’m assuming it isn’t going to support traditional three tick markdown code blocks, but instead some special block.
I know most people do not create open source projects to make money or to even get reimbursed for their time, but as a project gains success more than likely it will incur some expenses. It would be nice to have some sort of revenue attached to the project so you can cover those.
I’ve seen two basic ways of generating revenue in open source, the first is donations, and the second is by selling something, a commercial license, priority support or something else.
What is funny is how people look at the two vastly different. For example, if you say here is a way to buy something for $20 then people will either buy it or move on. It’s a simple business transaction.
On the other hand, if you say donate $20, the average person goes into a completely different mindset and they want to know what you are going to do with the money, are you going to be frugal, is it required, and on and on.
It’s interesting how people are happy buying things even when a company might be failing and could go out of business tomorrow, but when it switches to a donation they want to see a P&L, balance sheet, and ensure their money is going to be spent well.
On Saturday morning a missile alert was pushed out from the Hawaii Emergency Management Agency and according to the Washington Post this was the cause:
Around 8:05 a.m., the Hawaii emergency employee initiated the internal test, according to a timeline released by the state. From a drop-down menu on a computer program, he saw two options: “Test missile alert” and “Missile alert.” He was supposed to choose the former; as much of the world now knows, he chose the latter, an initiation of a real-life missile alert.
I can’t imagine how a designer, developer, QA, and all the other links allowed something this bad to even make it into production. Much less something so important as a missile warning system.
I can’t imagine how scary it would have been to be on the island when this was pushed out and it makes me think of all the cold war bunkers we still have peppered around our nation. Back then I imagine everyone would have had the thought of dying at any minute in their mind. Which if we are honest is not necessarily a bad thing since it would keep your focus on what matters most to you.