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.
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.
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)
Actually, we are working on adding support for TV/Kiosk mode where the components update the data regularly, and you aren't limited to showing only one set of components. The dashboard will slowly and automatically cycle through all different components so even if you have more widgets than your screen can handle, it'll still work better than not being able to work at all.
The main difference is that Dashing is focusing more on current KPIs and Metrics. While we believe that those are crucially important, sometimes they just aren't enough for people who have data that's too much to get condensed down to a single indicator.
Well, maybe you can take a look at another dashboard framework I wrote. It uses PHP, pulls data directly from MySQL and works seamlessly on mobile browsers, tablets. :)
We are going to release a version with PostgreSQL support shortly.
RazorFlow PHP generates SQL code according to the requirements and filters, and must take the differences between the SQL dialects of different vendors into account.
I have noticed most people have their email addresses publicly displayed (in some human readable form), or have web pages with ways to contact them. In that note, I have been contacted via HN before and have met some people as well. Considering the ultimate purpose of a Private Messaging feature is to allow communication between two willing parties - the existing infrastructure is already there.
Moreover, more influential people who very strictly value their time and privacy (Matt Cutts for instance) might not be comfortable having an open avenue by which anyone can contact them.
More importantly, if you have someone's full name, there's a reasonably high chance you can find a proper way to contact them - provided you are determined enough to do it.
The page seems down for me. Fortunately, I happened to find the text in the cache.
"Jeff Bone <jbone at place.org> on Sat Feb 24 10:09:30 PST 2007
Previous message: [FoRK] Bone's Corollaries to Philip Greenspun's 10th Rule of Programming
Next message: [FoRK] And then there's Haskell...
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Feb 24, 2007, at 10:38 AM, Ken Meltsner wrote:
> Odd that this has come up -- I was just looking at Common Lisp and
> Scheme implementations, as well as a smattering of Haskellish tools
And then there's Haskell...
Haskell is like "that girl." You know the one...
You never really went steady, but you'd run into her from time to
time while knocking around in disreputable joints, usually late at
night, every several months or so. She looked so hot, so sleek, so
sexy, so expressive, so exotic. You'd end up back at her place and
the night would just... take off. A complete blur of hot, sweaty,
feverish, delirious, fumbling passion. You'd do things to each
other... you'd do things to her, she'd do things to you... things
that you're not even sure have names, that you're pretty sure are
illegal almost anywhere. Even her kinks have kinks --- and after one
of these nights, you'd realize that you yourself had a lot more kinks
than you. And it wasn't just physical, it was --- cerebral.
Ethereal. Transcendent. But it would all whiz by in a blur, and by
morning you'd find yourself lightheaded, a bit confused, and
stumbling homeward to your regular gal.
Over the next few days and weeks you'd find yourself occasionally
drifting away, thinking about her. Haskell. You'd be there, banging
away at your regular girl, and find yourself thinking "you know, if I
was with Haskell, I'd be doing this completely differently." You'd
think "I could be doing so much bigger and better stuff with
Haskell." Now, your regular girl, she's not as exotic as Haskell.
Pretty, maybe, if you're lucky. (Perhaps your regular girlfriend's
name is Python. ;-) But not nearly as --- weird. Wild. Cool.
Exciting. Don't get me wrong --- your girl, she's wonderful. You've
got a wonderful relationship. She's --- comfortable. You can bang
away at her all day and night. She's accommodating. Easy going.
You work well together. But --- confidentially --- she's, well,
maybe just a little bit boring. You'd catch yourself thinking these
things, and the guilty pangs would get to you... You'd quash the
thoughts, buckle down, and get back to banging away. Comfortable...
there's a lot to be said for that, ya know? Comfortable... just
keep telling yourself that.
Months would go by. Late some night you'd find yourself out,
disreputable places again. Maybe that hacker bar, LtU. Somebody'd
slip you an URL for some renegade paper, you know, one of those
papers. You'd run into Haskell again. And the whole thing starts over.
Eventually, you're going to get the ultimatum. Haskell's ultimately
just like any other girl on some level; she needs commitment.
Eventually, after one night of wild, feverish, kinky, abstract
passion, she's going to say to you: "All these times, and you don't
understand me at all! You know, you're going to have to get serious,
mister! I've got needs, too. You're going to have to get serious
about my monads, or that's the last time you're going to play with
them! Got it?"
...and then, you've got to make The Choice.
Chances are, you're going to go back to your regular gal. Haskell's
just too much for any one man, probably. She leaves a trail of
broken, brainy, embittered PhDs and former programmers behind her.
She ruins you for the RealWorld. You can ride a while, but you
probably can't go the distance with her. Go back to your regular gal
and try not to think too much about what you've seen. Done. Felt.
Thought.
Maybe you can salvage a little happiness; but it'll be hard. After
all... you've tasted Haskell.
I think there was a project to do that - and smooth out another few emacs quirks. I don't know how much it's being maintained though, but it was built by Xah Lee (afaik).
I'm a vim user, not an Emacs user (though I have dabbled with emacs before). If you still use vim on the console, you can do a lot better.
There's a reason why vim has support for multiple buffers. That you can keep multiple files open simultaneously. Read about vim remoting, and you can use a single gvim instance (which offers better performance and font rendering), and edit all files in just that.
Even in emacs, buffers are everything. Nobody opens a new instance of emacs for each file.
[ my public key: https://keybase.io/skyronic; my proof: https://keybase.io/skyronic/sigs/6ld4MkNiejCqvm00oXosdjR1zyplfCzQvLZolV0RYH4 ]