geonik

https://twitter.com/Tendar/status/1672528514547953664?s=20

The pigeons surely concluded that RFC-1149 cannot compete with satellite broadband on technical merits alone, so they started sabotaging competitive installations with any means they have!

You may want to check https://whereby.com/, it works on the same principle, but you get to choose your own URL suffix, thus making link sharing easier.

Non-paywalled article

https://www.seattletimes.com/nation-world/chaser-border-coll...

There is! It is called Qooxdoo, exists for years, and works wonders around the impedance mismatch.

http://lmgtfy.com/?q=what+is+my+public+ip

When it comes to APIs, every now and then someone say "X is dead, Y is the future".

APIs are not a one-size-fits-all problem, and while general trends and paradigms are a nice thing to have, developers should not be restricted by whatever is the hottest buzzword today.

A nice and clean API will always be pleasant to use, and this has nothing to do with RESTful awesomeness or SOAP verbosity.

Greek startup owner here. Our government is trying to recover from a mistake by commiting a bigger one. Our Varoufakis-illusioned prime minister thought that he could force a better deal from Eurozone members by blackmailing with a worldwide economic Lehman Brothers moment. This obviously didn't work, and the referendum theatre was setup to cover up the failure. That in turn, is a huge gamble, putting the country's prospects for generations to come at risk.

I second that; Java has solutions for all problems described by this post.

- constructors, private fields, methods, addressing the "separations of concerns" - how about Enum.valueOf(enumClass, text.toUpperCase()) to avoid the "classic shadow array of string literals"?

Here is an example of what can be achieved by Java enums

  enum Type {
    ANIMAL(null),
    MAMMAL(ANIMAL),
    DOG(MAMMAL) {
      public void makeNoise() {
        System.out.println("Woof");
      }
    },
    CAT(MAMMAL) {
      public void makeNoise() {
        System.out.println("Meow");
      }
    };
    private Type parent;
    Type(Type parent) {
      this.parent = parent;
    }
    public boolean isA(Type type) {
      if(this == type) return true;
      if(parent != null) return parent.isA(type);
      return false;
    }
    public void makeNoise() { }
  }
  assert Type.DOG.isA(Type.MAMMAL) == true;
  assert Type.CAT.isA(Type.DOG) == false;
  Type.CAT.makeNoise(); // "Meow"

XPath for JSON? Who would have thought of that! Now add namespaces and you reinvented XML 10 years later

What a mess! And, frankly, I don't care unless I can read the source code

"the latter point is one of the reasons most people like to avoid XML"

And these are exactly those who will never "get" that XML is much more than a data container for tree-like structures. They should stick to JSON or CSV for that matter.

Those who rant about XML and XSLT know nothing about what they talk about. 50% of our server's behavior (200,000 Java LOCs) is orchestrated declaratively by a small number of XML files that use around 30 custom namespaces. These are

1. parsed on server startup for setting up persistence, business rules, REST endpoints etc

2. transformed by XSLT to a) produce nice HTML documentation, including DOT class diagrams b) generate Java source code c) validate declaration integrity and cross-referencing

With the right XSDs, IDE support is excellent (auto complete for everything). Take the time to learn it, apply it according to your needs, and reap the benefits- in the long run, maintenance work is down by an order of magnitude.

With default settings:

You scored 666 You are better than 100 %