It's a site with live camera feeds from around the world to see the sunset.
1,671 karma · joined September 1, 2010
It's a site with live camera feeds from around the world to see the sunset.
---
But... now let's think for a moment about what you're doing there. Not the technical bits, but what the user sees.
You have decided that the average male lives to 71-72 and female to around 74. You have then decided that this average should be taken as a hard, fixed limit. And that people will die at that age no matter what.
These two assumptions are somewhat tricky. I mean, the first one is fairly random without a context. For, say, India, this is about right, but for other countries of the world -or as an average for the whole world- it can be quite different. And you don't mention any particular country.
But anyway, it's the second assumption that is more problematic. Because the number is just an average and using it as a hard limit is clearly wrong. First of all because death is not linear. Take a look at this sample table for the US [0]. Life expectancy increases with age. That means that initial life expectancy can be 80 years, but if you make it to 60, your total life expectancy goes up to 84. And if you make it to those 80 your life expectancy still gives you -on average- another 9.5 years to live.
Why is this relevant? Well, because such a calculator would assume the user, the person that goes there to see how much time they have left with their parents... well, still has their parents alive. It would be stupid otherwise if they know their parents are already dead. So this is 2026. The user states that their dad was born in, say, 1956. That's 70 years. Is the 71.5 average life expectancy right? Not at all. Even as an average, even as a hard limit, it is wrong. For a person at 70, that life expectancy would be something like 80+ and the remaining time should be calculated according to that. Sure, this means you need to write code that is a bit more complicated than what you've done here. Because you don't just have one average life expectancy, you need a whole table or function to calculate it. But, hey, this is learning! It's a coding exercise. So it is an opportunity to learn more and go beyond the simple tutorial into an exercise that is just a little bit more advanced.
---
But then again, let's ignore even this. Let's go back and keep the simple exercise. Let's assume just one fixed life expectancy. Then, as I mentioned above, we have a problem that's worse, more... stupid. Because as I said such a calculator has to assume the parents are still alive. Otherwise is simply makes no sense. And yet, you're giving the user the option to choose birth years as far back as 1940, while directly assuming that anyone born before 1952 for men or 1955 for women is already dead.
When you offer that option, you're saying it is a valid option. But when the user chooses it, you're saying they are stupid for doing so.
What you're doing is like this conversation:
- Hi, I visit my dad every Friday afternoon.
- That's nice. But from this other perspective that may not be a lot of time. How old is he?
- Oh, my dad is 78.
- Bad news: your dad's already dead.
- What? No, he's fine, I saw him just yesterday.
- Your dad's been dead for years.
- You're an asshole.
---So... again, congratulations on your coding exercise. You did it. The coding is solved [perhaps]. Well done.
But take this as an additional learning point: The problems you solve will sometimes involve writing code, but they will always require you to think about the details and nuances of the problem itself. It's all about the decisions and assumptions you make.
Discussing this seems useless.
I think there's a fair amount of submissions and discussions: https://hn.algolia.com/?q=Qubes
Others can only be spotted from a distance. Wagtails are quite timid but can be seen running around sometimes, and the blackbirds can be heard a lot even if you don't see them. I've also spotted a couple of woodpeckers. And once the park fell suddenly still and I looked up and there was a kite passing by (they have been spotted nesting in a much larger park a couple of miles away).
If the park is busy, then I'll watch the dogs, people going by. I ponder about the futility of life. Just sit there silently, doing nothing.
https://news.ycombinator.com/item?id=47611866 ("Show HN: Agentmatic, AI marketing platform that generates full campaigns for you")
It has not been deleted, as you can see.On the other hand, I don't see any asking for reviews or feedback. What I see is self-promotion, similarly to your previous post from a couple of months ago, which is against the guidelines: https://news.ycombinator.com/newsguidelines.html
You'd probably need to detail what exactly you have done to clean up, but it sounds like you didn't actually remove the commit?
You can remove a commit with an interactive rebase and then force push the new tree. Or depending on the current state of your tree, you can use other options. In any case, you have answers to this on Stack overflow. e.g. https://stackoverflow.com/questions/40245767/delete-commit-o...
But in any case, it's not very interesting. I mean, there's not much of an insight about board games. Even after saying that they "give you a false sense of socialising" (emphasis mine), the author immediately notes that "This is not representative of board gamers - many board gamers makes lots of close friends through board games - but for me, I was not building new friendships through board gaming."
Note that you need a browser with FileSystem Access API support. It would be nice to mention that in the readme.
But "Show HN" has seen its use restricted for new accounts because of the large influx of spam on the site lately. So you probably can't do much.
Consider reading the guidelines: https://news.ycombinator.com/newsguidelines.html
As for the game... At first I thought it was going to be just ok. Nothing more than a couple of minutes and then move on. But then I ended playing a bunch of the puzzles in a row without even noticing the time. It plays very, very well and it's quite fun.
Congratulations.
> A: It's cooled through our large heatsink and ultra quiet Noctua fan. The fan only turns on above 75% brightness. At max power, the heatsink is cool enough to put your hands on it for a couple of seconds.
( Or if you prefer https://www.githubstatus.com/incidents/xwn6hjps36ty )
2. What email clients has the resulting HTML been tested on?
3. There are some problems with the "primary button" block. First there doesn't seem to be any way to change the button's colour. It's blue and there's no way to change that. The block that contains it has a white background which can be changed, but not the background of the button itself. Then there's the text colour -which by default is another poor option, green text on blue background- which you can try to change but when you press "apply changes" it has no effect, and when you click the element again the property goes back to showing green as the colour. The same happens with the "outline button".
4. In a "Text Content" -"paragraph with heading and text"- there are also some colour problems. The properties only show the text colour of the heading but not that of the text paragraph. But then if I do select a colour and apply changes, it only changes the colour of the text paragraph but there seems to be no way to change the text colour for the heading. The same applies to the "basic header", where you can change the colour of the sub-heading but not that of the larger heading text.
5. I can't select some text with the mouse when editing it. If I try, it tries to move the block. I can select a bunch of text if I use the keyboard -e.g. ctrl+shift+arrow- but it's hard to justify that I can't do it with the mouse in a so-called visual environment.
6. A "text content" block contains exactly 1 heading and 2 paragraphs. The second of those paragraphs says "Add more paragraphs as needed..." but there doesn't seem to be any way to do that and add any additional paragraphs to the block. For that matter, there also doesn't seem to be any way to remove a paragraph from the block.
I just tried something like...
let someArray = [
"one",
"two",
"three"
];
...and it warns that it's missing semicolons on all those lines -except for the last one, obviously-. And the fix is... Your code:
let someArray = [
Fix:
let someArray = [;
But then I tried something with an actual syntax error.It says...
Syntax Error
Line 1
ERROR
JavaScript cannot read this line because something is typed wrong.
...which doesn't seem very helpful, not even pointing where in the line the error lies (which acorn does tell you). So I open the dropdown to see the explanation and fixes. The explanation is... The code breaks basic JavaScript rules.
...and the suggested fixes are... Fix the typo. Look for missing or extra symbols like ), }, ], or ;.
So I wonder, what does this actually say beyond the original "syntax error"? How is it helpful at all?Also, looking at the code I find all sort of failing rules which just don't work.
"Assignment in condition":
This will show a warning, while being perfectly fine:
if (flag) a = null;
This will not show a warning at all: if (a = 2) b = 3;
Then there's the rules for unused variables and for undeclared variables. Those simply do not work at all. They never find anything. It looks like you're expecting acorn to modify your code so that you can later go through it line by line but it just doesn't work that way.