My main gripe was that each notification was a separate bar item that I had to clear out - five messages from the same person in the same app, is five notification bars in the menu. And the "smart" grouping I don't think fixes that.
I like MacOS okay, but re: notifications, they too have this abysmally small "X" to clear out notifications. They're just... annoying.
The goofy thing is that I remember when iOS used to be _better_ at notifications. Android didn't used to give you so much control over app notifications and iOS required apps to use them much more sparingly.
I still have issues with Android's notifications though. Some apps insist on using a single "General" category that includes both notifications I require as well as marketing and advertisements.
I'd suggest evaluating tools on an as-needed basis, instead of wholesale rejection. And I'd 100% agree that the article could've benefited from a "Why Haskell, specifically" section. But really, few things are unequivocally useless. (Or good, for that matter)
(I'd also suggest that you meant 'recoiled', not 'rebuked')
The article has nothing to do with Haskell, other than it's what I use. Why should I have to justify that when I want to talk about architecture diagrams?
Would the same expectation be in place of my examples were in JavaScript? I doubt it.
It's your article, you don't have to justify anything.
That said, it still would've been nice to hear if Haskell has bought you anything that other languages don't do.
Would I have asked the same question for a JS article? Maybe I wouldn't have asked - I'm a bit more familiar with JS than I'm with Haskell - but a "and here's why I picked those tools" section would still have been interesting. I like hearing how people think about solving problems.
The fate of writing in public: people will always ask for more info on the parts that they're interested in.
great idea. take some time and let work be your source of income and not your entire life. you won't get a do-over of your 20s. whatever you decide to pursue, inquire thoroughly about work/life balance. you can always go back to the startup grind later.
Yes, excellent point. Having built side projects and provided consulting for more than eight startups, I've grown somewhat weary of the never-ending pivots, dead ends, etc.
I haven't had a girlfriend in ages and have been living like a college student for way too long.
the keyboard is so small, why not just use your cell phone? yes your on screen keyboard is far from ideal but it has already built some muscle memory. typing on a tiny keyboard with a non-standard layout is just painful.
Eh. Not a fan of the small keyboard on the GPD, but I'd take that over my phone's keyboard any day, especially for programing.
I have 10 years' of muscle memory for on-screen keyboards, and I still find them absolutely painful to use for anything other than a few words. When sending text messages, I use voice transcription (with the awkward "exclamation point", "newline", etc.).
If I were to use this, I'd set it up on some surface and just 2-finger type it like old-timey authors did on their typewriters.
And, FWIW, 20 years ago I jerry-rigged together a few gender benders and a null modem adapter so I could use my Palm Pilot to interface with VT100 terminals. Using Grafiti to send control characters and navigate TUIs was... interesting.
It was not that I could type faster (a swipe style onscreen keyboard is faster than all non full QWERTY keyboards IMHO) but that when I was writing a lot, long text or terminal command it was much more comfortable.
in my experience, having access to the aws dashboard rarely indicates mastery of the platform and knowledge of which tool is best for the job. it is incredibly common to lift and shift on premise workloads to ec2 with an rds instance to save the cognitive load of application refactoring. this creates a different flavor of infrastructure complexity without taking full advantage of the services on offer.
i figure system settings are annoying because the default is good enough for most users.