HN user
I'd be interested to understand how this compares with a solution like openfreemap's (https://news.ycombinator.com/item?id=41635592) which was posted a few weeks ago.
What is it that sets this apart from other similar solutions?
My guess is the roast version looks at the repo details/descriptions (or at least a few of them - which is why the reply seems much more specific/cutting) where as far as I can tell the praise version here only looks at readme/top level profile info.
Hard to tell from the article if this is something specific to "social media" scrolling, or (as my guess would be) just a finding that reading via scrolling is potentially bad for your eyes.
Be interested to understand if other ways of consuming content (swiping pages or whatever) would be better, as I do almost all my reading on my phone these days, so would prefer not to screw my eyes.
Maybe it's a tech company thing but we were using irc for years before slack came about. We eventually swapped to hipchat as it was easier for less technical people to join, and later slack when that shutdown.
Almost every open source project I've worked on coordinated on irc back before slack/discord took over so it's hard to says text based communication tools are anything new. What I will give tools like slack is massively improving ease of use for less technical users, which has meant it's now used much more widely outside technical spheres.
Sounds like a good few of the directors were much old than that.
One listed director — at 942 years old — would have been born in the 11th century.
Honestly, in my experience most the "good" PHP jobs tend to end up in the start-up space, where pace of development/sheer ability to get stuff done (PHP's strengths) are the primary drivers. As you move to bigger companies, more specialised languages tend take precedence as they can afford the increased dev time in order to achieve greater efficiency/throughput.
I still love PHP, as I like solving problems and pragmatically PHP is really really good at that. But at the end of day, everything is a trade off, and the trade-offs of PHP don't make sense everywhere.
In terms of bigger places, facebook still hire plenty of PHP devs, Slack as well - or at least they used too. Bumble (and the network of related sites) was heavily PHP a few years back too. Etsy you already mentioned. Quite a few "non-php" places still have a fair PHP estate that needs looking after too, even if they are slowly migrating away from them.
I don't really see what the risk is. So far as I follow the ultimate threat from the mods is that if reddit makes the proposed changes to the API, they'll stop modding. Given the changes will take a way a lot of the tools larger subs rely on to mod effectively its an unsurprising move.
If reddit wants to step up and moderate the site itself, it's free to, but if it wants volunteers to keep working for free it'll need to play ball with em in some way or another. That or play chicken and see if it wins.
It does seem like most studies show WFH workers being happier/healthier/more productive. Wouldn't necessarily take that as conclusive, but i've certainly not found much evidence beyond random anecdotes saying the opposite.
e.g.https://www.forbes.com/sites/bryanrobinson/2022/02/04/3-new-...
I've used PASETO in place of JWT for this kind of thing before. Interested to know how it compares.
Does this support a known standard, or is it just its own thing.
Is there a way to console log / inspect the state of your entities?
<body><script>x=document;x.write`<input id=a><b id=b></b><p id=d>🆑<ul id=c>`,b[o='onclick']=b=>{b=x.createElement`li`;c.append(b);b.v=b[v='innerHTML']=a.value,a.value="",b[o]=e=>b[v]=(b[v]==b.v?'<strike>':'')+b.v;d[o]=e=>c[v]=''}</script>
https://jsfiddle.net/eqym2ac0/
Working with shrew. 240 char with script/html or 217 with as JS.
<script>x=document;v='innerHTML';o='onclick';x.body[v]="<input id=a><b id=b>X</b><p id=d>clear<ul id=c>",b[o]=e=>{let b=x.createElement("li");c.append(b);b[v]=a.value,a.value="",b[o]=()=>b.classList.toggle('y');d[o]=()=>c[v]=''};</script><style>.y{text-decoration:line-through}
Combining yours & the strike thru example, managed to get both strike thru & clear added in 277 chars. If i could save another char could close the p which would be nice :p
https://jsfiddle.net/hysjgkcm/
Down to 270 https://jsfiddle.net/vr7246jk/1/
Reminded me of the rocks xkcd https://xkcd.com/505/
Dyslexic's of the world untie!
I actually think a lot of people underestimate quite how many dyslexic people are about in industries you wouldn't expect them. I work in software development for instance and have worked with vast swaths of dyslexic devs, QA/test automation engineers and all sorts of other technical roles. A lot of the time its never really brought up as thanks to syntax & spell check its fairly hard to go wrong (I'll admit to having been responsible for a couple of pretty questionably spelt variable names tho).
Its really only in fully written out text it can become obvious as even with spellcheck, if you bungle a word bad enough (or somehow skip a few which i also do more frequently than i'd like), what gets fixed can sometimes be far more bazaar than the spelling error itself.
For the most part I think people develop coping mechanisms for the majority of day to day issues it gives them, although some bits Ill admit I've never been able to fully work around (I feel most 6 year olds would likely out do me trying to alphabetise a stack of books for instance) - not that its something that comes up regularly in my day job `book.sort();` :)
It's probably also notable that the stuff under the term "Dyslexic" vary's a lot - both my wife and i have it (future kids are doomed), and although we share a lot of stuff, some symptoms are entirely different. Its actually a pretty interesting thing to read up on - especially as a remember some of the info being pretty much none existent only a decade or so ago - while now there is are ton of research about in to what on earth is going on with it.
I'm always disappointed there is no standard for just sending markdown emails. They work fine as plain text, are future proof & any can easily be styled up an email client to fit with the rest of its design.
Always a shame to have to go full HTML email, just for some light formatting.
This fits perfectly with my own experience. The 3rd pass is always the one that makes the difference in terms of code that just feels nice/clean.
As a plex plugin? Be very interested to have a play once you release, been hoping for something along those lines for a while :)
I had exactly the same thought when I popped over to have a look at their readme. It's odd they don't mention it at all, as at face value it appears both Plex and Streama are both solving the same problem.
Would also have been interesting to hear what they view their edge as, as plex is already a pretty mature and powerful codebase, where as this appears to be very new. (I'd guess being open source would probably be their main edge right now)
To be fair to it, it does describe itself as "A shitty attempt at a honeypot/sandbox that uses docker" and contains a fairly large & up front "WARNING WARNING WARNING" section :p
The camel casing comment confuses me? There is nothing stopping anyone from using
var x = my_function();
var x = myFunction();
Got the same message & did some googling which resulted in finding this forum thread: http://forums.linuxmint.com/viewtopic.php?f=58&p=909267
Sounds dodgy to me.
I'm not the OP, but as someone whos both a programmer & dyslexic - I do it because i enjoy it & and IMHO am pretty decent at it. Sure I naturally make a few more typos in my code comments & docs than most people, but a minute of extra proof reading (+ F6 in sublime) fixes that so why should anyone care?
I'm sure everyone on your team says the same thing when you spell all your shit wrong and can't do 90% of the refactoring shit legacy code that they do.
I wasn't aware dyslexics magically got to avoid ever having to debug weird issues in legacy code bases? Hell, i may as well not come in some days if thats the case.
ugh, hn, get a grip seriously. Programming can be hard, that's the deal. It's not an every-one is the same we can all bring our special snowflake to the party deal
Sure, programming can be hard, and true, it isn't for everyone. But what has my (or anyone elses) being dyslexic got to do with whether they are the best person for the job?
I do exactly that, weirder still i can often tell the words on the page say somthing differnt to I'm reading while i'm reading it wrong. My fiancee does the same thing (we're both dyslexic).
This is pretty much my point of view. How new or buzz-wordy a bit of technology is, isn't really the issue. It's whether or not the thing in question will allow you to end up with a simpler solution.
Simplicity and supportability come hand in hand for me. I'd much rather debug/fix a really simple app in a language I don't know, than a really complex one in a language I do.