1,301 karma · joined June 4, 2012
"non-technical example of people using signals when players leave the board (in the bathroom, over a balcony etc) and in technical ways suggests that certain earpieces could pass checks or potentially other small devices"
Using older and more established languages seems less risky.
Say I wan't to install artifacts from two GitHub users. I would have to add these two Maven repositories:
- https://maven.pkg.github.com/USER1
- https://maven.pkg.github.com/USER2
In that case USER1 can publish an artifact with the same groupId/artifactId as USER2 and my Maven will happily install it without suspecting anything.Another case - someone deletes their GH account and another user takes it: https://blog.sonatype.com/hijacking-of-a-known-github-id-go-...
Docs: https://help.github.com/en/articles/configuring-maven-for-us...
- Central has a global namespace of artifacts. com.google.guava is the same for everyone. This will probably stay the default of open-source libraries.
- GitHub Package Registry has a per-user maven repository, so a local namespace (https://maven.pkg.github.com/OWNER). This is likely to be used by companies internally.
In order to use GH Registry instead of Central, I would have to add a dozen maven repositories to my settings.xml. I doubt many developers will be up for that.
Docs: https://help.github.com/en/articles/configuring-maven-for-us...
return jsonObject1.toMap().equals(jsonObject2.equals);
because JsonObject uses HashMap internally which supports equals(). The downside is it would be slower because toMap() creates a copy.Btw, downloaded java-commons as Maven dependency from JitPack: https://jitpack.io/#blobcity/java-commons
Unfortunately its quite difficult to get a fully reproducible build with Maven as the post points out. Even if you manage to replicate the build environment and settings, Maven produced binaries will be slightly different on each run. File timestamps are saved in jar files so they change on every build.
This vulnerability applies to Java deployments, typically in clients running
sandboxed Java Web Start applications or sandboxed Java
applets, that load and run untrusted code (e.g., code that
comes from the internet) and rely on the Java sandbox for
security.
This vulnerability does not apply to Java deployments,
typically in servers, that load and run only trusted code
(e.g., code installed by an administrator).
[1] http://www.oracle.com/technetwork/topics/security/alert-cve-... > I still missed something on top of Executors and CompletionStage.
You could use RxKotlin. It has Schedulers and Observables/Single/Completable for interacting with async tasks. https://github.com/ReactiveX/RxKotlinMycode -> facade -> library
Navigating code becomes more cumbersome and stack traces longer. I do like this approach too but it isn't free.
I like IntelliJ but do prefer Eclipse and am quite happy with it's core functionality. It's when you install all kinds of extra plug-ins is when it's starts to become less usable. But I've heard similar things about Sublime and Atom.
> The latest example is my former clients at Tokutek, who just
> got sold to Percona in a presumably small deal — regrettably
> without having yet paid me all the money I’m owed.I wonder why you wouldn't use PrestoDB to connect to Elastic Search. It provides you with an SQL engine and you just need to write a connector that knows how to get data.
Similar thing has been done in Crate.io.