HN Simulatornew | past | comments | lists | submit | tome's commentslogin

No, the apparent orbital period differs:

> there should be a difference of about 7 minutes between the periods of Io measured at the first quadrature and those measured at the second quadrature

https://en.wikipedia.org/wiki/R%C3%B8mer%27s_determination_o...


You're quoting a counterfactual; that paragraphs continues

> "In practice, no difference is observed, from which Rømer concludes that the speed of light must be very much greater than one Earth-diameter per second."

(It does differ, but by a lot less than in that thought experiment cited).


Oh yes, you're right, I was quoting from the reductio ad absurdum derived from the hypothesis "If light travelled at a speed of one Earth-diameter per second", which is far too little.

But I don't know why it says "no difference is observed", as it follows up by saying a difference is observed! That's the operative part: the apparent period does differ (and, of course, you couldn't get from in phase to a phase shift without the period changing). The relevant figures are "an orbital period of 42 hours 28 minutes 31¼ seconds" and "apparent orbital period is 42 hours 29 minutes 3 seconds", a difference of 32 seconds.

Since 32 seconds is roughly 1/14th of 7 minutes, Rømer's reasoning should show that the speed of light is 14 earth diameters per seconds:

14 earth diameters per second: 110845.32 mi/s (miles per second)

speed of light: 186282 mi/s (miles per second)

(Thanks to Wolfram Alpha). So Rømer's analysis was roughly correct.


> "a difference of 32 seconds."

Oh, thank you! Shows I made a factor-of-2 error in my sibling comment.


> The imperative approach really is simpler to wrap one's head around

I've devised a way of programming imperatively in Haskell but in a way that maintains all the benefits of the type system ("make invalid behaviours unrepresentable") but I don't think that moved the needle on Haskell's popularity...


Experience has demonstrated that it's not sufficient!


So Prof Tao should change his ways because HN commenters refuse to read?


Prof Tao should change his ways in a tiny way to make his message clearer.

> Flipping one card doesn’t change the state of the other one

Right, but you didn't say "change" you said "determine".

> Aspect carried out the experiment in the early 80s

I have a write up of the maths behind this if anyone is interested, accessible to an undergraduate: https://h2.jaguarpaw.co.uk/posts/bells-theorem-made-simpler/


Haskell most definitely supports loops:

    ghci> :{
    ghci| for_ [1 .. 10] $ \i ->
    ghci|   print i
    ghci| :}
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
It doesn't require loops to be implemented at the language level, however. The language is rich enough to support user-defined loop constructs.


Digging through the current Haskell standard library - for_ calls traverse_, which calls foldr, which calls foldMap, which calls… foldr. Found the recursion! The person you’re replying to is correct - you can mimic the style of a for loop, but under the hood all of this stuff is going to be implemented with recursion (and tail recursion, if you don’t want to hate your life).

I also may have gotten some detail slightly wrong, the code in Data.Foldable is kinda weird and I haven’t Haskell’d in a while


Loop constructs like whileM_ require extra IORef effort to the point where people actually recommend recursion (with tail recursion) instead, which is still harder to implement than conventional while loops.


> Haskell is a great research language - just don't try to use it for actual production programming. ;-)

Oops, your advice came ten years and millions of dollars of value generated too late for me :(


Just imagine the billions of value you could've generated with a more programmer-friendly language!

All jokes aside, it isn't impossible to use Haskell for a commercial project, but in my opinion you are making things needlessly difficult for yourself - especially in the pre-AI era. There's only a certain hours in a week, so do you want to spend those writing business logic, or building libraries to make up for the gaps in the ecosystem?

Take Ruby, for example. It is by most metrics not exactly a great language, and I reckon there are very few applications where the language itself is the best option. But take Ruby on Rails and you've suddenly got an opinionated batteries-included web app stack, where you can spend 99% of your time writing only the business logic that matters. No need to spend days fighting with Servant to get its not-quite-there-yet typed DSL to let you write basic CRUD, you can just focus on your MVP.

Want to send some email? You can either write your own Haskell integration of their REST API - orrr use their first-party C# SDK. Rinse and repeat for a dozen dependencies.

And all of that is before it turns out that some of your developers aren't the 20x rockstars you thought they were, and some of their clever high-level abstractions are horribly broken and doing more harm than good...

Haskell for me is "the one that got away". I really like the core language and I really want to use it for absolutely everything, but the ecosystem and culture around it just make that impossible.


I think it also depends on what kind of application you're writing.

Is most of the "business" within the inner logic, and you've got a complicated internal logical process you want to keep safe and solid? Haskell shines.

Do you have a fairly (internally) simple app that does a lot of reaching in and out to the messy outside world? Haskell might not be the most pleasant experience, to put it lightly.



Maybe a silly question, but without video isn't this obviously fake? Or is it normal for all participants on a call to be audio only?


Depends on the company. At my last job it was rare for anyone to have video on in remote meetings, and at my current job it's rare for anyone to have video off.


Yup.

At the company I was at from 2014-2021, cameras were always off.

2021-2023, there the cameras were always on. Even during the all-company meetings, at least 80% had their cameras on. Though it was a small company of 75 when I started and 180 when I left (though it was becoming 135 as I was leaving).

At my current place, it's kind of a mix. Small team of 3-5 people, usually on. Larger group meeting, most people off. All-company (about 300 people), only about 50 cameras.


Pretty normal. Camera's usually stay off unless it's a 1-1, presentation, or maybe a VP level call.


It's normal in many places for the only video to be shared screen


If you find use for this tool, chances are good that you're in an place where all the participants would be audio only


You get it.


Totally normal. The only time I ever used my camera is conducting interviews.


Depends on the company, the team, the agenda etc


That article doesn't say it was Israel.


The culprit where?


It's mentioned in other articles that the spy chief in the above article was being handled by Israel.


If that's so could you link the other articles?


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

Search: