popey456963

Google's Project Zero.

To be fair, you need _significantly_ less[0] uranium compared with the amount of coal you mine. For every million mountains destroyed by coal mining, you'd only have to destroy a couple of mountains. Not to mention I don't think uranium is usually mined from mountains but rather pit-mined, makes it far better than the alternatives.

Personally however, still support solar. Especially solar house tiles, they look good, pay for themselves after a few years and can be placed on every house.

[0] https://xkcd.com/1162/

Why on Earth could they possibly feel it necessary to do this? The United States Patent Office doesn't have a complex system of sub-domains or even an EV license, if money were the object then they could just go with Let's Encrypt (not to mention the current license continues until 2018 anyway).

The amount of computing power it takes to encrypt with SSL is minimal, especially if you use some of the newer systems like ECDSA and should not be of concern to a company like the Patent Office.

It is Friday? Roughly 4PM on Friday, which means they'll likely be closing down shortly. Seems odd for them to do it as such a last minute thing.

You can source Li-ion/Li-Poly fairly easily (as a company, almost impossible as an individual) with 250 Wh/kg, I believe I read somewhere that Tesla hit about 260/270 with their latest power walls. Even so, I still have to doubt they'll reach more than 200km range with current technology.

Their mission is to release to the public in 2025 however, which makes the goal much more likely to be hit with improvements in technology.

It's the first point they mention on the landing page:

- 300 km range - Travel from London to Paris in one hour.

Imperial (A UK University) are currently making large leaps forward in terms of modelling a room or environment with just a single camera and little computing power. Their basic methodology was:

- Pick "unique" points currently in view

- Track how they move as the camera moves

- Combine this data with the accelerometer to get an accurate movement reading of the phone.

- You can get the depth of any point by comparing two images and knowing the change in user position.

Simple algorithm, but their results were astonishingly good. Snap don't need to model the entire room, they just need to work out where these points are to keep the image appearing still.

I'm sorry, what's CEF? I haven't come across that acronym before.

> Is this benchmark open source? I'd be really interested to try it compared to something similar build in Qt or Gtk+.

Afraid it's not, currently the only working copy is closed-source whilst I work on rewriting it all into an open source repository. Having said that, I'm in no doubt that Qt or Gtk+ would be significantly faster than rendering what is essentially a local website.

> I really hate to think how it'd cope on an embedded device with an ARM processor. There's a marked difference to me between Atom and e.g. Sublime Text.

Reminds me of a joke told by a friend of mine:

Friend: "The thing I like about Atom is that it encourages you to write small files."

Me: "How does it do that?"

Friend: "Well, it crashes if you write more than a couple hundred lines."

Personally, I too do use Sublime Text. Not entirely sure how Atom is so slow, but it takes ten times longer to startup and five times longer to search through my files. Definitely caused me to switch away from it.

> but the fact remains that the UI is built on the DOM with interactions handled by JS

Excellent point, but I think if you're doing complex interactions that require a large amount of computing time then you shouldn't be using a program like Electron. For something like a mail application, not much changes. We actually never remove mail items, simply hide them from view, so we have one large render time at start-up and then almost none after that (displaying and hiding an element from view is incredible efficient). For something like atom, you have a significant amount more happening and you want just about everything to be instantaneous. Plus the fact that it's expected to be able to deal with large files consistantly without any hiccups.

I swear Electron is incredibly fast in every instance I've used it. Unless you're doing heavy computation with complex algorithms, it's really nice. I don't believe VS Code has to do any computationally expensive computations, and it enables many more people to work on a project (JavaScript being a truly universal language).

I'm currently working on a Mail application and my benchmark test case is an email account with 20,000 emails to be displayed. Noting we currently have no lazy loading and all these are loaded from an on-disk database and put inside their own Shadow DOM it truly did surprise me when it took just over 400ms for an entire page load on my development laptop (~3 years old with an i5, nothing special).

Even if you need to do complex algorithms, just write that particular part in C and use it in the rest of your JS code like normal.

Considering how we're doing now? Yeah, I'm pretty cool with how they handled things.

Would you perhaps consider working together instead of on two separate projects? Half the workload for both of us to get the same final product!

This site is actually really awesome, and has worked for every website I've tried! My only slight issue with it however is it took me a few minutes to actually work out what "HTML codes" were and even then it was only from watching the video. Have you considered renaming it to something like "HTML Source Code"? It also seems to struggle on web pages it can't find tables, such as the following website I made which contains no information:

https://hastebin.com/eguluvoquq.html

Pretty sure most applications don't need to support RFC 2177 to still be efficient. Long-polling for most IMAP servers requires one packet every nine minutes (to the best of my knowledge), which is literally nothing. It would take months of being run constantly to even get up to a megabyte of data being transferred. Some rough back of the envelope calculations:

- 10 minutes per poll, 1440 minutes in a day, 144 packets per day.

- 50 bytes per packet, 1,000,000 bytes to a megabyte, 20,000 packets required.

- Roughly 140 days of time, or 5 months to reach a single megabyte.

Aren't there some optimisations that are so minuscule it isn't worth implementing them?

Honoured to have your first post Benjie. It is open-source and made in Electron, but I'm not sure it's upto much at the moment. I've mostly been working on getting IMAP and SMTP setup as opposed to any graphical work.

If you're interested in helping out, I'd love any help I can get. Email me at the address on my profile page and I can give you some more details. The current design looks as follows:

https://puu.sh/vmtT6/b803a88da5.png

Must admit I am somewhat jaded with current mail applications and actually creating my own. Sylpheed is wonderful and the one I currently use, it's fast and works. My problem is with the GUI. Every single linked email client in this thread looks like it has come from 2005 and, unsurprisingly, most of them were created around then.

Hoping that maybe by using some more modern libraries, and aiming for a material design-esque client, I might be able to make something easy to use and reliable.

I'd honestly disagree. Start small, don't expect to build something that works for 100k users and you'll be fine!

Take the bare bones of this project:

- Canvas.

- Websockets.

That's literally it. You'll need to know how to draw on a canvas, and how to send and receive WebSocket information. You can quite happily keep the current state of the canvas in an in-memory array, perhaps saving it to a file every few minutes in case the server crashes. Then, perhaps, when that's done you can swap our your in-memory array for a REDIS bitfield, improve the web sockets to no longer use JSON, but instead binary? Both of which should be only a few tens of lines of changes, but after that you'll be able to support tens of thousands of simultaneous users with hundreds, if not thousands of changes per second.

The thing with this project that's complex is the number of users required to use this at once, lessen the requirements a little and you'll come up with a simple project.

Excellent work actually completing the challenge set! If you were to do it again, would you still use the same technology used here? Kafka especially seemed to cause you a few issues.

Haven't there been several of these posted to Hacker News already? All of which look almost identical.

EDIT: Ah, apparently they're all links to this page.

There's also no ability to uninstall Edge, the current way of doing it appears to be to delete all of the binaries in a specific folder.

My moderating day generally goes as follows:

- Look at the mod queue, replying to any mod mail we've received and any posts that have been automatically removed by our AutoModerator script.

- Have a peak at the new posts, on any one day my sub-reddits only get a couple of hundred, so it takes a couple of minutes for a cursory glance.

- List all reported messages and see whether they're acceptable.

Then, because most of the sub-reddits I'm currently contributing to are about projects I'm working on, I generally answer any questions people have or problems they're facing.

However, this is just for me. It really truly depends on the type of sub-reddit you're looking to moderate as to what work you're required to do.

Calm down, personal insults aren't necessary. I have to admit I've had the same experience, don't know my phone number and don't carry it with me for the majority of the time and I've needed it twice so far. Once for a Twitter bot and once for a Telegram bot.

Never before have I been asked for a phone number that hasn't been optional from any other service (of which I have quite a few, LastPass counts about 2,200 of them).

(Of course, sometimes I do still take the optional road, two factor authentication is exceptionally nice).

The article ends by saying "By the theorem, Koomey's law has the potential to be valid for about 125 years". One imagines that it could continue long after even this however with further ways of computations being discovered.

Even if you don't use the language specifically, the ideas it provides on creating queries applies to pretty much every database I've used, with the one exception being Redis.

It also doesn't hurt it's the most popular language at the moment and judging by the amount of applications using it, won't be disappearing anytime soon (especially not in just ten years).

This.

People forget that they're _actively_ appearing to break it by using this UA detection. No company should _ever_ use user-agents for feature detection, because user agents themselves are screwy in so many ways [0]. Honestly, I feel like this was someone actively deciding to break the system on Linux (or any unrecognised UA). Wouldn't any reasonable developer just send back a fully-featured page if they couldn't understand a UA?

[0] http://webaim.org/blog/user-agent-string-history/

100MB? Assuming they're using GZIP, that's normally a 10% compression ratio, leading to about 1GB of actual data. Let's assume this data is stored as 8 bits, that's about one hundred million characters of code! Maybe what they're doing is downloading the entirety of Windows XP (roughly a gig in size), running it in JavaScript and then rendering the page in Internet Explorer within their version of XP.

I'm actually more of a fan of https://www.ssllabs.com/ssltest/analyze.html - it gives you a whole lot more information (although does take longer).

I generally see prices of 2 cents per gigabyte per month for active storage, even less, most under half a cent per gigabyte per month for long-term archival. Assuming there were willing to fork out 10 dollars a month, they would be able to get around a terabyte of storage.

Lets imagine our average citizen uploads quarter of a gigabyte, that means 4,000 visitors uploading files per $10 client. Assuming you can keep other costs really low, it's not too outrageously expensive.

This would be pretty amazing, to have a shared base.

Considering the amount of Electron apps that I've now installed I must have at least a couple of gigabytes dedicated to just hundreds of copies of Chromium.

Youtube automatic captions aren't actually that bad last time I checked. They updated their algorithm recently (read: last couple of years) and on non-technical phrases it probably has about 95%+ accuracy with good audio quality.