Christian Humer

@grashalm_

Working on GraalVM. Making languages and tools fast and composable with Truffle. Member of the Oracle Labs VM Research Group. Expressed opinions are my own.

Zurich, Switzerland
graalvm.org
Vrijeme pridruživanja: ožujak 2012.
30 fotografija ili videozapisa Fotografije i videozapisi

Tweetovi

Blokirali ste korisnika/cu @grashalm_

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @grashalm_

  1. Prikvačeni tweet
    2. sij

    As a platform for new programming languages GraalVM is an easy sell, but people often ask, whether it is justified to reimplement language interpreters for it, when there is already a stable reference implementation. Here are five reasons why I think it is:

    1 reply 12 proslijeđenih tweetova 43 korisnika označavaju da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  2. proslijedio/la je Tweet
    2. velj

    “ is popular even across non-Java programmers and will increase Java's popularity in 2020.” This is a great prediction by and we will certainly work hard this year to make it true!

    2020 predictions:
    29 proslijeđenih tweetova 86 korisnika označava da im se sviđa
    Poništi
  3. 31. sij

    Every language has its use case. Brainfuck is designed as compact language to write secret messages to fellow computer scientists without going through encryption key exchange protocols.

    1 reply 3 korisnika označavaju da im se sviđa
    Poništi
  4. 31. sij

    Every time these Microsoft office guys show new dialog boxes with poor usability on startup I have to pay the price of scared family calls...

    1 korisnik označava da mu se sviđa
    Poništi
  5. 29. sij

    Keeping up with Github/Jira/Slack issues and getting things done is a real hard trade-off for me. If I'd have all the time in the world, I would always immediately respond. I am aware of the irony that I complain about this on Twitter instead of answering issues ;-) .

    1 reply 1 proslijeđeni tweet 5 korisnika označava da im se sviđa
    Poništi
  6. 24. sij

    If you are at this year. Don't miss this tutorial.

    Excited to announce that there's going to be a tutorial on " with and " at this year's ! ➡️
    1 proslijeđeni tweet 7 korisnika označava da im se sviđa
    Poništi
  7. 22. sij

    Love that GraalVM cover design.

    GraalVM und die Jagd nach der Performance: Das Cover des Jahres 2019 #2019
    3 korisnika označavaju da im se sviđa
    Poništi
  8. 17. sij

    Ok 16k lines removed. A good start :)

    It is feature freeze Friday. Time to remove deprecated APIs. To be merged right after the fork. :-)
    7 korisnika označava da im se sviđa
    Poništi
  9. 17. sij

    It is feature freeze Friday. Time to remove deprecated APIs. To be merged right after the fork. :-)

    8 korisnika označava da im se sviđa
    Poništi
  10. 17. sij

    Requiring data portability and full interoperability for market dominating social networks is a very good idea to nurture healthy competition. Privacy is a challenge to get right though. Anyone knows some legislative effort one can support so we get there?

    Poništi
  11. proslijedio/la je Tweet
    16. sij

    now use for almost a year in production. To find out why it is the best for web apps read here ( in russian ):

    15 proslijeđenih tweetova 59 korisnika označava da im se sviđa
    Poništi
  12. proslijedio/la je Tweet
    15. sij

    I agree with on all points here. we’ve conducted multiple experiments with implementing our in-house scripting language on GraalVM, and I’m confident that in the future this will be successful (AST interpreters don’t play nicely with preemption!).

    As a platform for new programming languages GraalVM is an easy sell, but people often ask, whether it is justified to reimplement language interpreters for it, when there is already a stable reference implementation. Here are five reasons why I think it is:
    Prikaži ovu nit
    1 proslijeđeni tweet 3 korisnika označavaju da im se sviđa
    Poništi
  13. proslijedio/la je Tweet
    14. sij

    GraalVM 19.3.1 is out!🚀 This is a regular critical patch update release and we recommend upgrading from older versions. Check the release notes: Download:

    110 proslijeđenih tweetova 186 korisnika označava da im se sviđa
    Poništi
  14. proslijedio/la je Tweet
    9. sij

    Back to work, follow up github issues from 2019 and... 🎆 updated for 19.3

    1 reply 7 proslijeđenih tweetova 23 korisnika označavaju da im se sviđa
    Poništi
  15. 7. sij

    Take a break if you start writing "this is stupid", or worse things, in docs.

    1 reply 3 korisnika označavaju da im se sviđa
    Poništi
  16. 2. sij

    5) Encourage language specifications: We have learned from JavaScript, C and Java that multiple implementations are beneficial to language ecosystems. This is because it requires language designers to specify features and be precise with dependencies on the environment.

    1 reply 8 korisnika označava da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  17. 2. sij

    4) Reuse of embeddings: The GraalVM embedding API is language agnostic such that work spent on embeddings does not need to be repeated with new languages. This allows to embed new languages in complex systems like databases with little additional effort.

    1 reply 4 korisnika označavaju da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  18. 2. sij

    3) Reuse across language ecosystems: GraalVM languages are composable, meaning they can be optimised and debugged together allowing the reuse of libraries between language ecosystems with little overhead and effort.

    1 reply 4 korisnika označavaju da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  19. 2. sij

    2) Reuse across language implementations: Effort spent on GraalVM components multiply to all the languages. A new compiler or GC optimisation often requires years of work. With GraalVM that work does not need to be replicated for every language.

    1 reply 4 korisnika označavaju da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  20. 2. sij

    1) Feature parity between languages: By having all languages similarly efficient and supported by tooling we allow developers to choose the right language for the task for the right reasons. The language choice should not be limited by performance or missing tooling.

    1 reply 6 korisnika označava da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi

@grashalm_ još nije objavio nijedan Tweet.

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·