Hacker News new | past | comments | ask | show | jobs | submit | thybag's comments login

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?


Functionally they are rather similar in what they're aiming for. Architecturally there are some differences.

OpenFreeMap uses the MapTiles format [1] which is an open source format for vector tiles that does require the attribution of the OpenMapTiles page for every map generated from it (CC-BY license). Versatiles uses the Shortbread format instead [2] which is published under a CC0 license. Instead of the SQLite based mbtiles format they developed their own container format (and a converter).

I've only started tinkering with this project a little bit cause I found it interesting after watching a CCC talk with it [3]

[1] https://openmaptiles.org/

[2] https://shortbread-tiles.org/

[3] German: https://youtu.be/8A51WkJ5S8I


There really seems to be a lot of movement in the map space these days!


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.


I don't even understand what leads to the exact conclusion that it is bad for the eyes.


Repetitive movements of tiny muscles that were never designed to do that kind of movements in the last millions of years of evolution and suddenly have to handle it hours per day.

That can be applied the same to pretty much every modern physical problem (diet, sitting all day, bad posture, carpal tunnel syndrome, &c.)


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.


That makes sense. What I really like about Slack are the integrations like GitHub and Jira, and commands like `/remind`, and the "Later" tab.


Same here, Slack is one in a long line if similar chat apps we've used over the years, on premises and remote.


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.


As much as us HNers like to talk about technology, moderation of content is the key to any social media platform being successful. Moderation goes away or drastically changes and the users leave when the site fills with garbage.

Occasionally mods will duck out for a day, on purpose, to let members go nuts with content. That is what would happen without moderators and after a while, all those un-moderated subreddits would become cess pools of bot content and spam with members leaving and traffic will take a giant nose dive.


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?


Yes! Not inside the tutorial, but in the 'real' game there is a console that you can log anything into.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: