Hacker News new | past | comments | ask | show | jobs | submit | querulous's comments login

the passthrough quality is a real letdown given the marketing. it's like looking at everything through a grimy, unwashed window

i never expected it to be good as a productivity device because my own experience is while screen real estate is nice what really matters is the ergonomics of your work space and wearing a pair of ski goggles is never going to be ergonomic


Opinions are mixed the passthrough quality: https://youtu.be/UvkgmyfMPks?si=ElAWNbsyEN6t_wmP


it's also because they wanted to run it at night with all the casinos (and the sphere) on the route lit up. the miami gp started at 1230pm and the montreal gp at 11am (930am and 8am vegas time, respectively) but the las vegas gp route doesn't look half as good in daylight


Skies are dark in Vegas by 6pm right now (and probably a lot more comfortable than it will be at 10pm, generally).


Yeah but that’s too early for Europe. It’s just an optimization problem across many dimensions. And rarely is the optimum there the optimum if you disregard all but one dimension.

Some combination of “strip looks better at night”, “showtime or post”, “needs to be viewable by Europeans” and so on.


the big risk with elixir imo is that it's runtime/vm is still owned by ericsson and there's no alternative. i know things like firefly exist but they aren't mature replacements (to my knowledge)


I thought Open Source Erlang is Apache 2.0 based on the first paragraph on the Erlang faq page [1]: "You can use Open Source Erlang to build commercial products without having to pay royalties or licence fees to Ericsson. Open Source Erlang uses the Apache License 2.0."

I think it is a bit confusing actually, since they differentiate between Erlang (the language), ERTS (Erlang Runtime System) and the BEAM. It isn't clear to me what "Open Source Erlang" refers to with respect to those distinctions, or what the licenses are for each of them.

1. https://www.erlang.org/faq/implementations


sometimes it's not your data


that presupposes that france wants to ban the phone. charitably they just want an accurate measurement so they can apply their regulations. the lab has no incentive to find either way


No, it presupposes this list of things unrelated to france or phones (or strictly speaking, only the last item on this list):

- companies engaged in government contracts would rather continue to be engaged in government contracts than have them be terminated

- politicians would prefer to say they spent your taxpayer dollars on something that caused a change which “benefited” you, rather than say they spent them on something that had no perceptible impact

- there exist technicians engaged in testing who believe the above two are true, and have the capacity to make micro-decisions in testbench setup that can affect the general bias of the results

That all said, based on the other commented here it seems french politicians took EU guidelines for 5mm exposure and demanded those same number at 0mm. So it really is the french politicians wanting to ban the phones.


this is 100% it. there's a ratcheting effect in owning housing in canada. that recent study about how 70% of homes in canada are being bought be investors is completely bogus. 70% of homes in canada are being bought by people who already own homes. often this is "investment" properties like rental units but a significant proportion of it is second ("vacation") properties and parents using their own equity to fund children's home purchases


it also advertises news, music and apple tv (and probably all their services, those are just the ones i've noticed)


it's not as mysterious as it sounds. every data structure (including modules and anonymous functions) has a binary serialization and every erlang vm is also an rpc server that can receive arbitrary data -- including whole programs -- and execute them. your vm of course needs to know about the remote vms to do so but that's where the rudimentary clustering mechanism in erlang comes into play


Also no shared memory in processes and they all communicate strictly through message passing, so running a piece of code in the local node, in another node in the same machine or in a node on the other side of the planet is a matter of telling which pid you want to send the message to, the BEAM will figure out how to send the message to the correct place in the cluster and your program will be none the wiser.


fwiw this is from 2018 and i would say the conclusion from those who were around pinterest at this time and shortly after would not be nearly as positive


how does the type system handle `receive` in erlang/elixir? does it just require every `receive` clause have a catchall case (meaning every `receive` is any -> T) or does it only guarantee type checking in the absence of external messages?


When you receive, we will use the pattern and guards from the "receive" to lift type information, but we won't verify the messages between processes in our initial efforts. Personally, as future work, I am more interested in typing behaviours, because that's how most users define and interact with processes.


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

Search: