logn

C++ -- https://github.com/mbasso/asm-dom

I don't know exactly how these work but Emscripten allows interop both ways (embedding JS in native code and calling native code from JS) -- https://kripken.github.io/emscripten-site/docs/porting/conne...

C, C++, Rust and others already have their own DOM/JS support.

WASM is exciting for statically typed languages especially. JS is not the target. It might eventually benefit from faster parsing but that's not the motive now.

I would like to have someone (a Java or Kotlin developer) take over https://github.com/MachinePublishers/ScreenSlicer and rework it. It's a project that intends to do exactly this. You enter a url, it finds a search box, enters the user's search query, uses single-layer neural nets and text munging to extract the search results, and then separates each result into a few fields (url, date, title, summary).

But it was written as a complete app and so is of limited use to most people. If it were remade to be a library it would have much more utility.

Beware there are lots of ugly regexes and terrible hacks. This is html afterall, the Cthulhu way.

Recently re-licensed from AGPL to Apache 2.0.

Also my time is busy on other things. I would be able to answer some questions occasionally but largely I can't provide much help.

It's a lot easier these days for young people to mess around with Ableton or Fruity Loops and make music alone than save every last dollar to buy a cheap instrument and try desperately to find the drummer and bass player which were always in short supply.

The guitar will be on more equal footing with every other instrument and hardware that musicians/composers use for live performance. There is still a need to perform music and people like seeing musicians do something, whether it's fiddle knobs or play an instrument. And there will always be something magical about an instrument that fully digital electronics will never have.

https://www.urmc.rochester.edu/encyclopedia/content.aspx?con...

In regard to boilerplate the author brings up an interesting point that with a good language, the boilerplate can effectively disappear once all the code has been written. If people are worried that boilerplate violates DRY, I think they worry too much.

The best way I've found to determine whether a codebase is good or not is to take someone who's never worked with the code before and ask them to fix a bug or make an enhancement. If that's an excruciating task but would have been easy in a greenfield project, the code sucks.

Anyhow to your point, I think the problem is that YouTube creators don't really think of themselves as being sponsored by brands. They've internalized only that they get paid to make content people watch. And that's not entirely accurate.

But for all the problems the author identified with adtech it has afforded people such as those on YouTube to enjoy what may be a fleeting era of getting paid to be genuine and uncensored. Perhaps membership fees to the platform that get allocated to creators can succeed here.

    public List<Integer> add2(File file) {
      List<Integer> resultList = new ArrayList<>();
      for (int i : ListUtils.emptyIfNull(file.getNumbers())) {
        resultList.append(i + 2);
      }
      return resultList;
    }

Step 4 requires no frustration. It should be a relief you can fix it yourself rather than hope for some opaque engineering team to maybe fix it at some future date since your company doesn't have the Platinum Support package.

> Steps 5..41: ...

I think maintainers of small projects should do their best to merge whatever is given to them without back and forth or delay--just a prompt and sincere thanks. There's no reason to treat contributors like junior devs you're trying to teach and guide. Sometimes that requires swallowing some pride in having the code be just right or means you may want to fix up a few things after the merge.

The Quasar instrumentation in my opinion is a pain. Out of the box you either get AoT instrumentation or you use Java agent command line option. Both were problematic for me in context of build processes, IDE support, etc. It's possible to do runtime instrumentation with no special command line option using the Quasar URL classloader and Ant task which scans classes to instrument.