Readit NewsI have wondered more than once and my browsing and searching skills are failing me on this one.
Edit: The closest link I can find is "Call me maybe" but I am not able to find a causation or even a direct link or mention for now.
(you can still see it in the url)
But the main difference is that DGG chooses ads based only on search term, as opposed to tracking you and collecting your data across the entire net.
If they wouldn't be personalized, the answer would be no, instead of "for the most part, no". Lawyer speak.
> Are these stories personalized to me?
> For the most part, no. Most recommendations on your new tab come from a general list of the best of stories on the web. But Pocket is actively exploring ways to deliver personalized recommendations in a way that vigorously protects users’ privacy. Importantly, neither Mozilla nor Pocket ever receives a copy of your browser history. When personalization does occur, recommendations rely on a process of story sorting and filtering that happens locally in your personal copy of Firefox.
The author has a totally reasonable set of requirements: React + TypeScript, writing posts in Markdown, small amounts of interactability, and static site generation. It may be an indictment of the JavaScript ecosystem and the current state of the web that nothing exists that can help the user accomplish this out of the box, but that doesn't diminish the validity of the author's requirements. (It's also possible that next.js, Gatsby, or another framework can actually support these with relatively little configuration.) But we should applaud the user for wanting to create a totally statically generated site! (I noted that Gatsby's homepage was not static generated and clearly takes a second before displaying content.)
Given that the author wants to render to static HTML, I interpret React + TypeScript to primarily mean JSX + TypeScript. Is this really any different than saying Liquid + Ruby, or Go templates + Go (used by Jekyll and Hugo respectively)? JSX and React's component based system were literally designed for HTML, and I'd argue it is definitively a better solution than the raw template libraries offered by other languages. You get automatic "syntax"-checking of the HTML by using JSX. By using JavaScript you have proper control flow instead of the awkward in-line conditionals and loops in templating libraries. A Component-based system makes code-reuse significantly easier. And by using TypeScript you can get type-checking for all of this. Unfortunately, using JSX and TypeScript means that you need some sort of build pipeline, and that's where the current state of JavaScript really rears its ugly head and adds a lot of complexity.
Writing posts in Markdown is also totally reasonable, as is wanting to support small amounts of interactability in future posts. A couple of comments mention that you could just add raw HTML to a Markdown file and call React from there, but that doesn't solve the compilation problem. A lot of comments also missed the desire for interactivity. It's for a developer blog! I'd love an interactive inline demo or explanation!
The blog title might have been a little overstated (the ideal tech stack), and the "zero memory of how we used to build forms in the pre-React times" isn't a great look, but I do think the actual content is solid.
Unfortunately it's proprietary, but there's another native client called gtkcord3 [0] that seems to be progressing well.
Why? Not trying to be snarky, just genuinely curious, I'd expect that those people would generally be less susceptible to advertising.
We built Linear as we’re frustrated the practices and the available tools when it came to managing software projects.
On the product, we especially tackled the performance problem. Everything is synced to the client and we sync just delta packages between the cloud and client as changes happen. This way all actions a happen instantly and navigating around the app is really fast. And the app works offline too.
We also streamlined the UI and UX, overall we are rethinking what comes after agile for software development. I think many teams looking for something simple to run their teams.
Our announcement post: https://medium.com/linear-app/practices-for-building-linear-...