elsen

Hi there HN'ers,

I've been working remotely for a few years now, for various companies and clients.

One itch I needed to sratch is timezone conversion. It's always a mental effort to figure out when someone in your team will be around, and to compute when you should schedule that meeting so that everyone invited gets a "respectable" time.

Here I present you whena.re, the most intuitive timezone viewer for your team ;)

It's been live for something like a year now, lots of people use it and feedback has been great so far,

I released a Slack integration so I'm hoping this will convince some of you to give it a shot if you've never tried it before!

Happy to discuss some more if you have questions or comments,

tl;dr: governance is hard, there's no silver bullet, every system may be tricked. "good blockchain governance" would rely on gathering the result of multiple "coordination flags" like a user vote, a coin vote, core dev decisions, etc.

Very complete "here are the limitation, in the end, just don't be dumb" article.

About the bribing part: Could we get rid of it if voting is anonymous (I can't reward you with a bribe), and we give right to coins that haven't moved for a certain amount of time (I can't ask for your money and your account has to be "old enough") ?

Since I couldn't find any explanation on the article:

Snaps are containerised software packages that are simple to create and install. They auto-update and are safe to run. And because they bundle their dependencies, they work on all major Linux systems without modification.

Appears to be a packaging systems for (desktop) apps on linux with auto-updates and stuffs.

Interesting "we must learn/accept/fight to cohabit" view, It's super American - Westerners centric though, what happens if decentralised currencies take off in emerging countries?

I like the idea,

I'm miss one thing: the minute someone says "I'd buy 100NIL for X ETH", the IFO becomes an ICO no? We just added an extra-step.

Thanks for sharing, I'm curious to see these circles lighten depending on project activity (releases, conferences, etc).

I want a similar platform with reproducibility built in: your paper gets in the blockchain, if and only if, its results can be reproduced by other members ("Proof Of Reproducibility").

Exactly my cliché of the Clojure community: a discussion about simple things like testing and tooling becomes a place to brag about some random features of Clojure. Insulting my patience (or the original author) on the way is a new one.

You're just confirming my last point, professional Clojurist? Enjoy it. Others, be warned.

You mean complex is easy, simple is hard?

His experience matches most of mine:

I've been learning & trying to use clojure(script) for ~2 years now. A few things I miss in every other languages:

- The REPL: I usually don't need a debugger,

- Figwheel: that makes frontend dev a pleasure,

- reagent/reframe: are incredibly straightforward, there's no special syntax, no special constructs, just a few functions, a few concepts (dispatch / subscribed) and you're done,

- core.async: based on a simple channels / pipeline paradigm

But then you get into the practicalities of testing & writing code. Shady special cases[1][2], annoying testing tools[3], useless stack traces. And other issues everybody knows. Simple things that become a 30 min discussion with 3 different libraries and 2 blog articles to go through[4].

To me, there's this hardcore group of clojur'ist that seems to be hyper productive and keep introducing new concepts. And the "rest" (me at least), that are floundering. You fight with useless stacktraces? Boom, transducers. You deal with buggy test runners? Bam, a new specification library with test generations.

I've started moving my code to ES6 and Go. The community is filled with helpful people, but it seems to me that if you're not writing Clojure professionally already, the language is becoming less and less relevant.

[1] https://github.com/replikativ/superv.async/issues/2#issuecom...

[2] https://clojurians-log.clojureverse.org/clojurescript/2017-0...

[3] https://github.com/bensu/doo/issues/134

[4] https://clojurians-log.clojureverse.org/clojurescript/2017-0...

You may not know: on Unity you can saturate / desaturate the windows. I set them almost black and white and increase the saturation when I need it (shift + brigthness up / down).

I have no idea if it provide health benefits similar to the "orangy filters" but it's pretty nice on the eyes and, personally, it makes me happy to see the outside world with brighter colors than my screen.

You miss the point, they want you to do more mental maths :)

I'd love to get a thoughtful explanation for mid-2012, I understand it as a rewrite + removing "wrong" design decisions made in 2009.

https://news.ycombinator.com/item?id=13104807

Click on the eye icon. You won't be able to run the notebook code, which would be a surprising thing to allow without some sort of authentication.

Unread status is managed remotely (sync'd between devices), so you should be able to query it with an API like https://api.slack.com/methods/channels.history

I wouldn't want such a distraction on screen at all time though.

CPUs turn watts into performance. A 45W CPU will deliver 3x the performance of a 15W CPU.

Can you provide a reference for this?

I'm pretty sure a CPU turns watts into HEAT and PERFORMANCE,

The 15W you're talking about is the TDP, which describe HEAT. This tells you about battery life mainly. Ghz is the unit of PERFORMANCE.

Actually some kinda does:

"Garbage collection is simulating a computer with an infinite amount of memory". https://blogs.msdn.microsoft.com/oldnewthing/20100809-00/?p=...

We both agree, I'm just using this as a pretext to share this intriguing piece of knowledge. I find the concept much more intuitive than "getting back unused memory".

Especially when you look at the 90% memory usage on your OS, it still make sense with the "infinite memory simulation" definition.

I can't speak for the others, but I did install Ubuntu on my 2014 MBP, to ease the transition to a future non-Apple machine.

They took 95% ownership of Aldebaran Robotic a while ago, and it's a huge success in Japan. I'm no expert but isn't that building a vertical?

AFAIR the robots are running on Intel Atom, but well... embedded... ARM... (not saying that's the only reason though)

[0] could be an XKCD joke. Ho wait... it is: http://xkcd.com/1700/

In the last Windows 10 update, if your username contains nadella, the spying services are disabled and your machine gets 10% faster.

I've spend 5+min on both and couldn't figure out which countries are covered.

Tor Browser... You mean Loki?

Sooooo, it's Quora/StackOverflow with anonymous mode by default and the wording "search" instead of "ask" and no gamification system?

I like it anyway, any idea how it's supposed to scale? I mean we've all seen a bunch of knowledge bases that are pretty much useless as they reach thousands of almost-similar questions.

UI is buggy: can't edit an item in the "additional list", the cursor gets moved to the end after each stroke.

Nope, you've seen it all.

There's a link in the coming soon to a talk schedule by some guy. If like me you're not particularly into Scala, just curious about it, you just wasted a click.

These guys: http://www.iskn.co/ Have a similar product that is compatible with any notebook and any pen.

Not sure how the Moleskine works but this one is an "active system": you need a device gathering the data while you draw but it's definitely worth taking a look.

I was expecting a left-padding robot as a demo.

Nice, the help image could be smaller to fit on the screen.

A typo would yield a "Unable to resolve symbol" Error in Clojure and a Warning in Clojurescript. Both at compile time.

Cursive IDE (IntelliJ based) has no problem renaming functions.

These are all tooling issues, not specific to Clojure nor Dynamic Typing. Give it time & give it a try!

Exact, this is a very simple parsing that works 99% of the time.

As outlied by mattmanser, the standard for non-remote is ONSITE. Which is respected by most of the posters this month.

True, pavlov's comment is about readability, not superficial design.