1,932 karma · joined February 2, 2011
Most replies are written in the quick-reply box (no parent) because they are responding to what is being said in the last X posts. Assuming orphan posts are top-level replies to the topic is nonsensical, and you can verify this by toggling on threaded-view on forums that support it.
The next best thing is to just link the upstream post from a post that quoted/replied to another, which is what Discourse and traditional forums already do.
Traditional forums have other issues, but longform discussion among multiple people over periods of time is possible.
I'm just curious how that's an upside to using a relational database from the beginning when your plan is to migrate to a relational database anyways.
Switch out "Mongo" for "Postgres" in your bulk paragraph and you have the same scenario but with less work on your part and more features to help establish your data model.
One upside I can see if it you're more familiar with Mongo where using a relational database slows you down.
Denormalizing on day 1 (Mongo) has you making guesses about your data access patterns at the worst possible time instead of just thinking about the data itself.
https://github.com/elm-lang/package.elm-lang.org/tree/master...
Obviously every service has different trade-offs to consider, which is why "Tor traffic is always worth it" is HN comment idealism.
The status quo already is to keep on using what we're using. That doesn't need to be said. But if it wasn't for our endless search for nirvana, people would be stuck on Vim and 4-space tabs.
No developer left behind.
In practice, callbacks become a problem when you need conditional async logic. Like if you have your simple callback pyramid but want to fork the chain at some level and merge it back at the end.
What would've been a basic if-condition with promises/await is often an invasive change with callbacks where your only tool is to extract and rewrite logic into helper functions. A simple conceptual change easily blossoms into heavy indirection where taming the complexity becomes an engineering feat.
At the end of the day, we all have different appetites for trade-offs.
Open the game and follow the mouse with your eyes while you click each 8-directional edge of the game's viewport and then click the center.
Now you can let go of the mouse (don't need to move it out of the game) and the game should follow your gaze.
This demo is impressive. It's accurate enough for me to isolate the orange ball from the cluster.
On a website, the calibration could be done in a modal overlay. "Look at this dot while clicking it wherever it appears". After then Nth click, the modal goes away and the user lands on the website ready to gaze.
Kind of like how keys are reused in Vim yet have similar meanings across each mode. You don't have to remember so many unique keybindings.
Some editors let you switch between panes with keybindings, but once you have more than a few or some in weird shapes, you end up needing tmux's `C-b q` pane selector. Seems like gaze could replace most of that.
> Do adolescents today have this kind of relationship with bands?
The big difference is that CDs would cost $15 a pop. $15 being the perfect price point for me, as an incomeless preteen, to get just one CD for my birthday and maybe one in my Christmas stocking. And then I'd be stuck with those CDs for a year. Or stuck with the one CD I had loaded in my portable player during school or family road trip or furniture store excursion.I was stuck with Radiohead for a long time. I remember I'd get so tired of listening to a CD that I would pull the headphone jack a millimeter out of the slot. It had the effect of muting the bass frequencies and sound terrible, but it sounded different. Breathed new life into my meager CD collection when I discovered that lifehack one day in sex ed.
I happily upgraded out of the CD era as quickly as I could, but I can look back and appreciate how well it forced me to get to know the few artists I had in my collection. Though it also came with a certain destitution of choice.
Spare us next time, please.
The dying business model is easily-detectable, obvious ads that can get defeated by NoScript or a regular expression.
It's death by a thousand papercuts for my mental load.
As an example, in this case with the /issues page, redirecting to `/login?redirect-to=/issues` would be more user-friendly since it signals that the page exists but you must authenticate.
The problem with Clojure is those developers that just copy and paste code off Stack Overflow. Clojure is just so darn composable that it probably really causes problems for people out there with those copy-cats on the loose!
I start projects with the template:
lein new compojure my-app
Ring quickstart: https://github.com/ring-clojure/ring/wikiRing API docs: http://ring-clojure.github.io/ring/
The top-level comment is asking for good ways to paginate. OFFSET works on localhost and with hundreds of rows. My solution is one that works in production once OFFSET fails you. For me, it was day 2.
At which point you could assign each post in a topic an indexed `position` column that always increases from 0 within that topic, which lets you jump to arbitrary pages and parameterize perPage.
fromPos = (page - 1) * perPage
SELECT *
FROM posts
WHERE topic_id = $1
AND position >= fromPos
AND position < fromPos + perPage
ORDER BY id
For simpler needs, your "Next" button could load items that come after the last ID on the current page but with a LIMIT. <ul>
{% for item in items %}
<li>{{ item }}</li>
{% endfor %}
</ul>
<a href="/items?afterId={{ items[items.length - 1].id }}">Next</a>
SELECT *
FROM items
WHERE id > $afterId
LIMIT $perPage
That's fast and really easy.And bit.ly gives you analytics. That's their service.
For a task I'll use whichever editor needs to least amount of learning, re-learning, and fiddling.
It amazes me that there was a time where I learned Emacs just for Clojure.
Only 31 people died during the Chernobyl meltdown, according to its wiki page.
The nice thing about an earthquake or tsunami is that they kill and then go away.
http://blog.izs.me/post/2353458699/an-open-letter-to-javascr...
Either way, no matter your preference, the issue is resolved by having a linter, not by scrutinizing your code for missing semicolons. The OP post feels very dated.