This is super impressive - both the pedigree of the team and the approach you took.
The funny thing is - when I first saw ploy, I didn't take it very seriously since so many of the signals that used to signify quality (decent design, copy, hard technical problems) are easy to fake. Plus the "grow while you sleep" space is crowded with weak players.
I wonder what the new markers of quality will be, which would separate the hand-crafted (to the extent possible) work v/s slop.
agree that many of those markers of quality are now low signal. Ultimately we let our customers vote with their wallet
Funnily enough, we spent a long time on our brand. From our launch video that has human actors, to our product details. I believe a distinctive, high quality, well implemented brand is still a hallmark of a strong product or service.
nit's defaults go beyond what --short does. The token savings come from stripping headers, padding, instructional text, etc. Headers and decorative text ends up tokenizing poorly, so it helps quite a bit there.
Chad's neighbor is looking pretty good at this point after Chad started enforcing retroactively added time limits that were not part of the original terms.
Having built desktop software - I found doing things cross platform is hard for various reasons.
1. You can't use any specialized features or APIs in one OS unless you implement it in all others.
2. If you use Electron you're basically building a webpage, which can only be taken so far in terms of user experience. While teams like VS Code have pushed the limits, you still can't do what this app is doing.
3. Increased test/QA surface area which becomes difficult - especially supporting Linux - which have relatively fewer users but you still have to properly invest time into supporting it, something startups cannot do.
I really don't see the point of this product, but there are plenty of small to medium teams which are mac only, and it's better to be an interesting niche rather than yet another collaboration and huddle-type software.
Hi! I'm Andy and I have 12 years experience in a wide variety of roles - web applications with a variety of technologies and desktop applications and networking applications with C++.
I have been at my last role for about 5 years and am looking for a change to focus on a Senior Full Stack Engineer role.
Sadly gogs for whatever reason doesn’t seem to actually use connection pooling or proper caching. It runs a new SQL query for every load of the "explore" site or a repo, which means I end up getting less requests/sec out of it than with gitlab.
+1, I use Grav too for my blog. Admin panel is really light, there's a lot of skeletons based on modern templates and they are a much smaller number which can be bad but also good so that you don't get overwhelmed by crappy stuff like it happens with Wordpress.
I first thought cool. On second look I see it is based on PHP. I'm sure newest PHP is really fast and advanced but I don't want to invest any of my time on that language (just my personal opinion).
Update: OK, it also runs on nginx. Made a wrong claim it does not run on it. Sorry.
Well that shouldn't be true. Firstly there is no good reason why any PHP framework would ever require a specific web server, so the claim seems dubious. A little reading in their installation guide confirms Grav should work with any web server: https://learn.getgrav.org/basics/installation
If anyone's looking for similar functionality for PHP (Database-level time-grouping, time-ranged drilldowns, charts), you can check out http://razorflow.com
(Disclosure: I am the developer of RazorFlow, and am only posting here because I feel it's relevant to this particular story)
The funny thing is - when I first saw ploy, I didn't take it very seriously since so many of the signals that used to signify quality (decent design, copy, hard technical problems) are easy to fake. Plus the "grow while you sleep" space is crowded with weak players.
I wonder what the new markers of quality will be, which would separate the hand-crafted (to the extent possible) work v/s slop.