smallsharptools

6 ms·

1.
Batty: A Multiplexer Built on Ghostty(batty.sstools.co)
3 points by smallsharptools 4mo ago|1 comments
2.
by smallsharptools 4mo ago
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.
3.
by smallsharptools 12y ago
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?
4.
by smallsharptools 12y ago
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&#x
5.
by smallsharptools 12y ago
FreeBSD is plenty fast. I expect Digital Ocean simply needs to work out some kinks. It will be fast soon enough.
6.
by smallsharptools 12y ago
No
7.
by smallsharptools 12y ago
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.
8.
by smallsharptools 12y ago
@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 o
9.
by smallsharptools 12y ago
Is it possible or does it make sense for GCC and LLVM to work together? Or does the licensing make that impossible?
10.
by smallsharptools 12y ago
Agreed. Click bait.
11.
by smallsharptools 12y ago
Get off my lawn!
12.
These Are Not The Hackathons You’re Looking For(sstools.co)
2 points by smallsharptools 12y ago|0 comments
13.
by smallsharptools 12y ago
HealthKit is just the name of the library. Health is the name of the app. Good luck with you lawsuit.
14.
by smallsharptools 12y ago
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 rapid
15.
by smallsharptools 12y ago
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 p
16.
by smallsharptools 12y ago
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 sor
17.
by smallsharptools 13y ago
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 devel
18.
by smallsharptools 13y ago
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.
19.
by smallsharptools 13y ago
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.
20.
Kobra – Real-time collaborative code editor with built-in video Chat(kobra.io)
14 points by smallsharptools 13y ago|7 comments
21.
by smallsharptools 13y ago
We should listen to this guy. Not many guys can pull off a striped shirt that well.
22.
by smallsharptools 13y ago
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
23.
by smallsharptools 13y ago
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
24.
by smallsharptools 13y ago
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. Brib
25.
by smallsharptools 13y ago
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
26.
by smallsharptools 13y ago
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 pai
27.
by smallsharptools 13y ago
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 de
28.
by smallsharptools 13y ago
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'v
29.
by smallsharptools 13y ago
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
30.
Bribe developers to fix bugs(bribe.io)
38 points by smallsharptools 13y ago|30 comments

More ›