[go: up one dir, main page]

  • 8 Posts
  • 317 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle
  • They explained it more clearly later in the article. 4 weeks for the first year, then 1 week for each additional year of tenure. So a three year employee would get 4+2, which is the same as in Canada. But a 4 year employee would get 4+3 which is less than the statutory (1+1)*4 in Canada.

    In Canada, once you get to about 6 years of employment, you can start to expect (1+1+2) * (# years). With a cap of about 80 weeks. You’d bust past the woeful 26 week cap with just 7 years of service.

    And, BTW: You would need 23 years of tenure to hit that 26 week cap.




  • It used to be much, much tighter, but I’m going back to the 1990’s for this. Back then you needed to have a real-life presence across the country to get a top level .CA domain. Otherwise you needed to get one in a provincial subdomain, like .QC.CA or .ON.CA.

    Provinces might even demand that you get a municipal level subdomain.

    But no more.

    I seem to remember needing to show proof, like articles of incorporation…but that might have been for getting a VeriSign certificate.

    Last time I registered a . CA domain there was no verification of anything.











  • My wife and I are dual citizens born in Canada but with fathers that were born in the UK. We decided to get our passports pre Brexit because we are planning to move to France soon.

    We’ve never lived in the UK, but had no problem getting British passports. We just needed our fathers’ birth certificates and marriage certificates. And, of course, our own birth certificates.

    We renewed our passports back in the fall, just before this news broke.

    PS: We are old enough that our mothers’ nationality didn’t matter, even though they both were born in the UK.






  • I’ve seen people mention this a few times, but I’m not so sure that it’s actually a thing.

    Switches are designed to route traffic intelligently, and they don’t blast all of the traffic to every port. If I remember correctly, at some point they do some kind of mapping between IP address and MAC address, and they know which MAC addresses are attached to which ports, and they only route the traffic to the port that has the MAC address they are looking for. I don’t know how much local switches collude with each other to share information about connected devices or how many hops they may be able to look into.

    In any event, no matter how wrong I am about that, if you’ve got a device on switch A that needs to send packets to a device on Switch K, then Switch A either has to know that the device is on Switch K and the path to get to Switch K or it has to send the packet to every switch that it is connected to. That doesn’t change with VLAN’s, if Switch A doesn’t have knowledge about every other switch on the network, and which VLAN’s they are configured for, then it will have to send the packet to every switch it is connected to.


  • Compose is great for Android because it’s so integrated with the ecosystem. For desktop applications, JavaFX - especially coupled with Kotlin - is a clear winner to me.

    I should point out that I don’t use FXML or SceneBuilder, but code all of my layouts in Kotlin. Kotlin features like extension functions let you eliminate 90%+ of the JavaFX layout boilerplate.

    Back to Compose. Both Compose and JavaFX are Reactive GUI environments, although many (most???) people don’t realize that about JavaFX. But both environments take opposite approaches to Reactive design.

    Compose, as the name implies, uses what I call “compositional reactivity”. This means that the actual layout is totally static, but is recomposed, in whole or part, in response to changes to the data representation of state. That code will look at the various State elements each time it runs, and alter the layout according to their current values.

    JavaFX uses “Reactive Layouts” (my term, again). JavaFX has a comprehensive, yet extensible, collection of Observable data types and another comprehensive, yet also extensible, collection of Bindings to allow you to connect them together in any way that you can think of.

    Every configurable element of every screen Node in JavaFX is expressed via these Observable values, meaning that they can be bound in some fashion - in either direction - to elements in the State data structure.

    The result is that it JavaFX the layout code is run exactly once. But this layout code not only performs the actual layout, it also creates the bindings to State. After that, the layout behaves dynamically all my itself.

    In JavaFX, layout composition is actually quite expensive in terms of performance, and recomposition is to be avoided if possible - and it is virtually always possible. I have seen people bitch about JavaFX being “heavyweight” and raggy, and I can guarantee you that those people are just doing a lot of recomposition.

    The biggest challenge to programming, and I say this with more years of experience than most people reading this have been alive, is in understanding the underlying paradigm that governs whatever language or toolkit they are using. Unfortunately, you unlikely to open up a book or webpage and see, “The underlying paradigm of this technology is…”.

    That’s especially true of JavaFX. It takes a LOT of time to realize the Reactive nature of JavaFX by yourself. Consequently, I don’t think that JavaFX gets recognized as the desktop application powerhouse that it is. As someone who has mostly mastered it, I’m constantly amazed at how trivial it is to build truely complicated applications with JavaFX.