Hacker Newsnew | past | comments | ask | show | jobs | submit | more lambda's commentslogin

And an HP48 emulator is still what I use on my phone as a calculator.

For the reason you mention, I need to get into the habit of using Calc for my quick calculations; right now, I usually use Google (ick, infix notation) or dc.


I've have Free42 on my Android phone. Do you have a particular emulator to recommend?

--

http://thomasokken.com/free42/



Thank you. I saw that one. Some of the more recent critical comments (stability, responsiveness) gave me some pause.

I'll give it a go.


I'm the same! None of the native RPN apps even come close.


RPN is so efficient when you are running a series of calcs when you learn it. I feel icky now if I use algebraic input or calculator and I have to backspace. It's like using a word processor, not a calculator! I am in Emacs all day for all things. It is a big mess of a world I like muddying about in!


Why would you think it was a single person?

Many of the large transactions are likely payment processors moving bitcoins into and out of exchanges, not any individual. Or mining rig operators cashing out to finance their power bills (and I'm talking the big mining operations, not someone's one or two miners in their apartment).


If you read the article, you'll see:

> Lincoln Stoll’s k8s-vpcnet, and more recently, Amazon’s amazon-vpc-cni-k8s CNI stacks use Elastic Network Interfaces (ENIs) and secondary private IPs to achieve an overlay-free AWS VPC-native solutions for Kubernetes networking. While both of these solutions achieve the same base goal of drastically simplifying the network complexity of deploying Kubernetes at scale on AWS, they do not focus on minimizing network latency and kernel overhead as part of implementing a compliant networking stack.


But if you follow the link the under the "components" section of your link you will see the link to the project proposal:

https://github.com/aws/amazon-vpc-cni-k8s/blob/master/propos...

There they clearly state:

>"To run Kubernetes over AWS VPC, we would like to reach following additional goals:

Networking for Pods must support high throughput and availability, low latency and minimal jitter comparable to the characteristics a user would get from EC2 networking"


How does it compare with Romana? They added a VPC router specifically for large K8 clusters on AWS.

https://github.com/romana/vpc-router


Both the Lyft and AWS CNIs use ENIs, Romana's CNI does not. But more specifically, vpc-router works along with Romana's IPAM to aggregate routes so that each VPC route can forward traffic for multiple instances. So, instead of one route per instance, you need only 1 routes per n instances. Where n is set by how much aggregation you want (configurable).

The net effect is that you can build large clusters without running out of VPC routes and no overlay is needed when traffic crosses AZs.

When a route is used to forward traffic for multiple instances, the target instance acts as router and forwards traffic to the final destination instance. This works because instances within an AZ have routes installed on them to the pod CIDRs on the other instances in the zone, so any one of them can perform this forwarding function.

Romana only piggybacks routes when there are no more VPC routes available, so for small cluster it's just like kubenet. For large clusters routes it uses all the instances to forward traffic so that none of them become a bottleneck.


Casino dice are actually cubes, at least as close as manufacturing tolerances of 0.0001 inch can make them. For example:

https://www.casinosupply.com/collections/casino-dice/product...

This is to help make it easier to spot alterations or flaws which could affect their randomness; shaved corners become very easy to spot, when packing them together it's easy to spot ones with height differences, etc.


Tolerance you’re referencing relates to the distance of one side to another, not the shape of the corners; the dice you linked to have their corners rounded (aka shaved) if you look at the image.


Indeed. I think anyone who has done some work with a milling machine will know firsthand that a freshly cut 90 degree edge that has not yet been rounded over is sharp like a blade.

If casinos actually did use dice that were extremely cubic, the dice would be cutting patrons' fingers and wrecking the felted surface of the craps table.


Funnily enough, the website the parent linked actually calls them " Transparent with razor sharp edges" so I guess they are pretty sharp.


I may have been wrong in my previous post. Apparently "razor" is one of several styles of dice edge and is intended to prevent excess tumbling, so a craps throw doesn't take too long to come to rest. I'm tempted to buy some new razor dice to see for myself.

I can't find measurements for the radius of curvature on razor dice edges, but I'd be surprised if they're truly as sharp as claimed. Without even considering the liability aspect, it seems inconvenient for a casino to pause the game because someone is bleeding on the table or dice.

I also wasn't able to learn how often the felt of a craps table is changed, though I came across something that said the felt's useful lifetime is prolonged by a foam rubber underlayer.


The first amendment applies to the actions of govnerment officials, not private parties.

In the meat-space analogy, the mall is still able to kick out people for violating its rules on conduct, but government officials are not allowed to, nor are they allowed to ask the mall to kick people out on their behalf.

> Trump can just drop twitter

Can he, really? It is his favorite medium, the one that allows him direct access to a large base of devoted fans, and allows him to state his mind publicly in a way that is not filtered by aids, media organizations, and the like.


In what way would a private site (say, a self-hosted GNU Social instance) not allow Trump direct access to a large base of devoted fans, and allows him to state his mind publicly in a way that is not filtered by aids, media organizations, and the like?


From the rendered manual that is linked from TFA

https://dspinellis.github.io/unix-v4man/v4man.pdf

> This manual was set by a Graphic Systems phototypesetter driven by the troff formatting program operating under the UNIX system. The text of the manual was prepared using the ed text editor.


Thanks. I was looking on the linked site and the README in the repo.


One reason I could see is if upgrading in place is substantially faster or cheaper than migrating data to new ones.

For instance, if the nodes are storage nodes in a redundant storage system, taking each one offline briefly for a reboot, and letting the others handle the slightly higher load, is a lot quicker than spinning up a new node and replicating all of the data over there so you can de-provision the old one.

Also, even if they don't have a lot of data, the time and resulting expense of spinning up and provisioning a new node while the old one is still online could add up to higher costs than just performing a reboot during a point of lower load.


> For pretty much complete nonsense NIH and standards-lawyering reasons.

You consider the fact that there is no spec other than "how the current implementation works", so no way to know if the code than works on version n will continue to work on version n+1, and no way to produce an alternate implementation, is a "complete nonsense reason"?

I also believe that it wasn't just Mozilla, but also Microsoft that scuttled this. Mozilla was the louder voice, but Microsoft never supported it either.


> You consider the fact that there is no spec other than "how the current implementation works", so no way to know if the code than works on version n will continue to work on version n+1, and no way to produce an alternate implementation, is a "complete nonsense reason"?

Yes. Sqlite is among the most stable and mature software in existence. I challenge you to name a single browser technology or API that has been anywhere remotely as stable as Sqlite, especially as implemented. As mentioned elsewhere ITT, Hwaci has contractual commitments to support backwards-compatible Sqlite3 for at least the next 35 years.

At that point, if I had to guess, "web browsers" won't be around any more, the web itself will be a dying or dead legacy technology, and companies yet to be founded will lead the tech sector, while Apple, Google, Microsoft and most likely of all Mozilla will be IBM-style dead letters or Digital[1]-style dead.

Sqlite was primarily written by one person and is maintained by three people.[2] If for some reason Mozilla had to fork or take over maintenance of Sqlite, it wouldn't even be worth noticing in their budget. It would, in fact, likely cost considerably less developer time than they spent designing, implementing and lobbying for IndexedDB.

More likely, if Sqlite3 were no longer being suitably maintained, all the browser vendors, plus the hundreds of other major tech companies that use it, would jointly endow a Sqlite Foundation to take over maintainence, which might cost Mozilla 5 grand or so a year, ye gods.

Even if Mozilla felt compelled for some reason (avoiding dependencies?) to rewrite Sqlite from scratch, Sqlite is 125k lines[3] of ANSI C compared to Firefox's 18 million lines[4] of C++, so Sqlite represents roughly one month of Firefox development time.

Firefox, Chrome, IE/Edge and Safari all make very extensive use of Sqlite internally, including to implement IndexedDB, so, obviously, Mozilla does not actually consider dependency on Sqlite and its API to present a meaningful risk.

Further, as things stand (and as they stood in 2010), Sqlite's massive footprint in the Firefox codebase means Mozilla already must rely on Sqlite remaining maintained, just the same as if WebSQL had been standardized.

> I also believe that it wasn't just Mozilla, but also Microsoft that scuttled this. Mozilla was the louder voice, but Microsoft never supported it either.

MS, especially at the time, ordinarily tried to slow or stall the standardization process for web technologies in general, so IE wouldn't fall too far behind. I expect better of Mozilla.

Mozilla was also by far the loudest (really the only) voice against WebSQL; MS barely participated in the conversation and was mostly noncommittal when it did. It's unlikely MS would've objected at all if Mozilla hadn't given them the opening.

[1] https://en.wikipedia.org/wiki/Digital_Equipment_Corporation

[2] https://sqlite.org/crew.html

[3] https://sqlite.org/testing.html

[4] https://www.openhub.net/p/firefox/analyses/latest/languages_...


> A signed app is only more secure if they load absolutely no code remotely

Which they don't. That's why it's not a web app.


> (This is not an official Google product)

It appears that Google's policy is that all open source personal projects be hosted under its GitHub account. Thus, I think "Google open sources" is a bit misleading; that implies that it's an official project being used by Google, whereas this just looks like a personal project being hosted by Google due to their requirements.


Yes, we've updated the title “Google open sources Bottery – bot-making language/platform” to that of the project. This is one reason we ask submitters not to editorialized titles: it's all too easy to mislead.


There's a (large) middle ground between "personal project" and "official product". It not hard to imagine a project being build as a proof of concept as part of someones regular job, yet not making it to "product", much less "official" status (and never intended to), but still open sourced because it might benefit someone else.


I don't think so. They've released their internal guidelines here: https://opensource.google.com/docs/iarc/

In this case, the person seems to have opted for the easier "go/releasing" route where Google retains the copyright. But that doesn't seem to strictly mandate using GitHub either.


I bet releasing a project with /google/ in it is a pretty good way to make sure it hits the top of HN though, so it's probably an appealing choice. ;)


I am also confused with that statement because the files appear to have Google Copyright in them. Example https://github.com/google/bottery/blob/master/js/bots.js

So its not official Google Product yet has Google Copyright. Not sure how that works.


Google doesn't support it in any way (=not a product), it's just something the author made during her time at Google internally (=it has Google copyright) that's now open-sourced.

https://twitter.com/GalaxyKate/status/925159463807361024


A Googler once told me that any code he writes during his employment with Google belongs to Google copyright-wise.

If they want to open source anything they have to ask Google for permission. It doesn't have to be hosted under the Google GitHub organization though (take Camlistore[1] as an example, although their primary repository is still hosted at googlesource.com).

This also means that if you want to contribute code to an open source project started by a Googler you will have to sign the Google CLA.

1: https://camlistore.org/


I don't think that's true for every project, as I have contributed to an open-source project[1] started by a Googler, and never had to sign a CLA, nor is the project hosted under the Google Github org.

1: https://github.com/benvanik/xenia


See my reply above.

TL;DR: Google's employment agreement means Google owns the copyright, which is what you see here. That doesn't mean we are endorsing the repo or making any claims to its importance.


> Not sure how that works.

I guess she wrote it at work.


Hey ho. I'm Chris, I'm on Google's Open Source Team.

One of the replies was right to point out this URL here: https://opensource.google.com/docs/iarc/

The key passage is this:

> As part of your employment agreement, Google most likely owns intellectual property (IP) you create while at the company. Because Google’s business interests are so wide and varied, this likely applies to any personal project you have.

We have two systems for Googlers to release code. We want Googlers to open source stuff. It makes everyone happier. So we have one method, which is really simple and pretty fast-track, usually taking about a week. That's what you see here: Google retains the copyright, we release it under Apache 2 to a Google-owned GitHub organization. The repo owners can then patch their repository without further approval steps (Google owns the copyright on that new work too), accept patches (as long as the submitter has signed the CLA) and we trust owners to act with common sense (e.g. don't change the license :) ). If the Googler leaves the company, they are free to fork the repository.

The other method is IARC as detailed in the URL, where a committee has to approve that the work is something that Google is OK with handing the copyright over to. I think the most common example is Googlers who write games, but of course people have all sorts of reasons for why they want to hold onto the copyright.

We recognize the challenge that comes with releasing repositories under the Google GitHub organization, but for those repositories to be not official. Headlines like "Google open sources [x]" is legally true but not spiritually so: the original author is the person who really open sourced and owns it, and Google is not really putting its institutional brand behind it. We have to balance that with the fact that we really need to know where all our repositories are, and be able to administer them, such as enabling CLA checks and forcing 2FA. The GitHub setup right now means that means putting repos under orgs we control.

We've spoken before about having a separate org that the non-official repos sit under, but this has always presented its own difficulties: if a project takes off, when does it "graduate" to the main org? What breaks if that happens? (Go code would for sure) What if the author feels they should graduate but we don't? Would projects in the non-official org not get the attention they deserve? etc. etc. Given that it's not a clear win, we've not opted to do that.

That said, I feel like I've seen the "Google releases [x]" headline on Hacker News more of late, and I am not sure if that's because submitters are excited and editorializing, or if there's genuine confusion. I'd love to hear any thoughts people have on that.


Hey, not a directly related question, but why does the individual Google CLA require a home address and phone number?

The policy at https://opensource.google.com/docs/cla/policy/ talks about minimal personal information collection and says "The two pieces of information that should always be collected from CLA signees are email address and name" — but the form at https://cla.developers.google.com/clas has way more required fields :(


We need to be able to identify everyone as part of our legal responsibilities. I'll take your comment to the legal team to see if there's any flexibility on the address/number requirement.


> That said, I feel like I've seen the "Google releases [x]" headline on Hacker News more of late, and I am not sure if that's because submitters are excited and editorializing, or if there's genuine confusion. I'd love to hear any thoughts people have on that.

Yes, I've been seeing this a lot lately too, and am frustrated by it because it seems to imply a much bigger commitment on Google's part than "this is an employee's personal side project". Hence why I posted the note.

Thank you for the clarification on the exact policy; since I'd been seeing a lot of these side projects posted under the Google account on Github, I figured it was something like that, but it's nice to see it spelled out.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: