smallsharptools

Ghostty is a great terminal app. I've been using it a lot over the past few years. When I started using Claude Code the tabs were not enough and so I looked for a multiplexer. I did not like tmux and other apps needed better UX design. So I made Batty using the Ghostty library and I think you'll enjoy using it. It has themes, keyboard shortcuts for everything, drag & drop to move window panes and fast navigation as well as notifications for terminal BELs.

Perl 6 was supposed to be an upgrade but it kept changing. I lost interest and know I will never use it. And if it is a totally different language why is it called Perl?

Perl was the language that I used many years ago but I moved on. Perl 6 was announced in 2000 and took over 10 years to see a release and by then most developers moved on like I did. When a language takes that long between releases there's clearly a lack of enthusiasm and support for the language. And touting market share? That is a pointless argument. You should be working with multiple languages and move past these silly blog posts.

FreeBSD is plenty fast. I expect Digital Ocean simply needs to work out some kinks. It will be fast soon enough.

No

I love that. From 1983 no less. It is basically the same sort of rant/argument you hear today. I will be sharing it with the undergrads I know.

@Animats, this is very true. Many only want to use languages which are considered easy. Ruby and Swift are examples of the easier languages which allow developers to avoid issues like memory allocation bugs. I do find that the side effect of using simple languages, relying heavily on frameworks and easy to use dependencies leads to complex applications which the developer does not really understand. The extreme example is a WordPress site which is slow or buggy and the "developer" who put it together does not know why much less appreciate what is going on in the MySQL database. I wonder how many developers are even capable of doing this low level work in relation to the total number of people who call themselves developers.

Is it possible or does it make sense for GCC and LLVM to work together? Or does the licensing make that impossible?

Agreed. Click bait.

Get off my lawn!

HealthKit is just the name of the library. Health is the name of the app. Good luck with you lawsuit.

Nope. The arguments in this piece are way off base. This is also now a very old argument which has been rehashed too many times. Modern wisdom shows us that native mobile apps have their place and Apple, Google, Mozilla and others are rapidly advancing web technologies. They are hardly holding back in order to force developers to build native apps. Once SVG, Canvas and other powerful HTML5 features become more common along with a more powerful runtime for the web, we will see the situation change. For now, I am happy building and using native mobile apps. I also build responsive web pages and plan on continuing doing so. They can coexist and they should.

My issue with how things work currently is that logging into a native mobile app is not nearly as easy as logging into a website. That process has to improve. That why I like logging in with Facebook, Twitter or GitHub.

Still what I would prefer is a single trustworthy service which does not compromise my privacy for the purpose of advertising. I could use that service to log into any service which would integrate with this single service to get a one-time password to the user on the computer or mobile device they are using.

As the user I would be able to use an mobile app and browser plugins to get the one-time password to conveniently log in with as few steps as possible.

I'm not sorry. He can disagree with other people and make decisions about his own life, but once he gives money to a cause that is working to restrict the basic rights and freedoms of others he's crossed the line.

I'm not sorry one bit.

Eventually you will get a handle on AutoLayout and it will become much easier. I learned to follow a few patterns that I taught myself which are solid for my interfaces. If I did it all in code I would be shooting myself and any other developer who has to touch this project later.

Who says designers need to use Xcode and IB? They can provide the comps so the developer knows the dimensions. It should be a collaborative process, not something that belongs to the developer or designer.

No thanks. Just learn to Storyboards already. It is it that hard and Xcode can help anyone who maintains this app. If it all in code it takes a lot of the and effort to understand what is controlling the layout.

We should listen to this guy. Not many guys can pull off a striped shirt that well.

What does this guy know about Open Source? It's not like he dedicated years of his career encouraging Microsoft to warm up to Open Source or works at GitHub to make it easier for developers using Windows to use Open Source.

Or wait, he has done all that? Next you'll tell me he's super handsome and has a beautiful family. Now you're just pulling my leg.

We have been looking at Bounty Source. We think jobs on Bribe.io will not be on that scale. Some of those projects are quite involved while Bribe.io may be smaller efforts, like updating a WordPress plugin to be responsive for mobile so it works with a mobile theme. It may just take an hour and earn the developer $100.

There may be some crossover with Bounty Source which could be good to provide multiple resources for users and developers.

We envision that many times the bugs will be fixed by someone who has not already been working on that Open Source project. We also do not expect any projects which are intentionally buggy to become popular enough to make a difference.

Bribe.io will also include work on enhancements to an existing Open Source project.

We have been looking at Bounty Source which has many similar ideas. It is tied into GitHub while Bribe.io will work with any source repository or issue tracker. Bribe.io may also work with smaller tasks while Bounty Source looks like it is taking on very large projects.

Got a link for that debate? The name is meant to get some attention while it is our intention to help users find developers who can help them make updates to the software they use but cannot update themselves.

And the developers getting paid to make these updates may be college undergrads or someone who has a day job but dedicates sometime to working on the jobs set up on Bribe.io. They can make some money helping others while also contributing to OSS which helps everyone.

The way we are going to handle the money is to take the payment when someone creates a job. The money will be held in an escrow account. Then developers can work on the job and submit their solution. Once the user accepts the work by the developer the money from the escrow account will be released to the developer. There will be a fee for the user while the developer gets the full amount pledged.

If there is a conflict we can step in to resolve it and make a decision. Since the money is in the escrow account it will not be possible for the user to just not pay and the developer cannot just take the money and run before they user accepts the solution.

I joined the project and made the same suggestion. Brad likes calling it Bribe so we are going with. It may make it more interesting and get more attention this way.

The bottom line is we want this to be a system that helps people. I've been at the mercy of open source projects which don't stay on top of known bugs which I am not always able to fix myself. I personally would love to task someone who is better prepared to take on the work to take on the job and I can focus on what I do best.

We hope that the vast majority of users will not exploit users. There are also many businesses which rely on open source software but there is no system for them to find and pay capable developers to fix bugs or implement new features they need.

One area we have discussed is Wordpress plugins. There are thousands of users using various plugins which may need some updates. They need to be updated as web browsers change and perhaps someone really likes a Wordpress theme but it has not been adapted to work on mobile. This scenario would be a good for Bribe.io which would help lots of people.

We will allow multiple people to join in on a bribe to up the amount to recruit developers to work on the job. So if there are 10 Wordpress users which all put in $10 it may be enough to give a developer the incentive to spend time to take on the challenge.

Look up UIDocumentInteractionController. It's been around a while.

You can also do quite a lot with URL Schemes but more apps need to implement support and publish their requirements.

There is also the X-URL-Callback spec which could be implemented by more apps. Google is using this spec on iOS.

http://x-callback-url.com/specifications/

https://developers.google.com/chrome/mobile/docs/ios-links

https://developer.apple.com/library/ios/documentation/uikit/...

Finally, let's get away for guessing about what Apple might be doing. It was easy enough to search "iOS open in" to find this support to support this feature and it had been around a few years. There's no reason to suggest that Apple is copying Android on this feature.

This is surely the end of the world.

Pass

http://brennanmke.github.io/Portfolio/

I created a basic portfolio to share on GitHub. I'd like to see more developers do that. It's quite easy to do with markdown and GitHub Pages.