Preferences

g0wda
Joined 179 karma

  1. oh nice! I didn't know that you can just make it use light dom.

      protected createRenderRoot() {
        return this;
      }
    
    And that's what it takes! I like using tailwind/utility classes so for the styles I'd need to have layers of compiled css files rather than one giant one.
  2. Something about Lit/web components that's not written clearly on the label is the hoops you have to jump through to style elements. If you're using tailwind in the whole app, you just want to pull it into your custom elements without much boilerplate. My main app compiles a single minified app.css, it felt not so modular to now include that in every single component. The alternative is create a subclass that injects tailwind into Lit components. It'd be perfect it just had a switch to inherit everything the page already has.
  3. If you now have a function where you call this one with an integer literal, you will end up with a fully inlined integer answer!
  4. Multiple-dispatch is the right abstraction for programming mathematics. It provides both the flexibility required to create scientific software in layers (science has a LOT more function overloading compared to any other field.), and the information required to compile to fast machine code.
  5. Location: Boston Remote: Ok with it! Willing to relocate: yes, to anywhere reasonable Technologies: Analytical database design and implementation, Technical/Numerical computing, Julia, Python, Elixir, C, Lisp Resume: https://shashi.biz/resume.pdf Email: (in resume)

    Summary: I've worked with the Julia community for 9 years as a professional and a student. Just finishing up my PhD at MIT now. Have been on a lot of varied projects so far, from web development to distributed computing, looking to do some exciting work in a place where I can use my skills, pick up new ones, and have some agency. (Not necessarily Julia, any decent technology will do.)

  6. Incredible release!
  7. Prof. Alan Edelman gave a nice lecture about this a couple of days ago https://www.youtube.com/watch?v=IuOXXQR7dAo
  8. In Julia, there is one package manager and it gets things right. https://docs.julialang.org/en/v1/stdlib/Pkg/ It's super nice to have no fragmentation when it comes to packaging. In Pkg, package states are immutable, always reproducible, and quick. Julia packages that have binary dependencies usually build them all for every platform using the binary builder infrastructure (https://github.com/JuliaPackaging/Yggdrasil). It makes cross platform installation robust and testable, and suuuper quick. Pkg really is the rolls royce of package managers.
  9. > I like the reactive notebook concept. It does really help with bugs

    Can you say more? An example, maybe?

  10. The basic Dask-like functionality is in Dagger.jl, we have plans to move out the distributed array functionality out of it and keep just the scheduler in there.

    I'm working on a set of functions to work with many DataFrames (or anything) in parallel and do it out of core if possible, it's basically like JuliaDB but with a FileTree abstraction rather than a table abstraction.

    http://shashi.biz/FileTrees.jl/lazy-parallel/

  11. Why not make one for yourself? ;)

    julia> (∘)(f, g) = x -> f(g(x))

    ∘ (generic function with 1 method)

    julia> (sum ∘ rand)(10)

    3.397728240035534

    Tip: type \circ<tab> to get ∘

  12. The generic function is the basic unit of abstraction in Julia. And this is exactly what makes Julia a very powerful language.

    If anyone is interested in reading more about Julia's design, I recommend Jeff Bezanson's thesis https://github.com/JeffBezanson/phdthesis/raw/master/main.pd...

  13. Responsiveness is excellent when your Julia process is on the same machine as the browser - which in itself addresses a large set of use cases scientific computing audience has (such as presentations). When the Julia process is connected over the network, there is obviously a lag between updates. But it's no better or worse than an AJAX/WebSocket application. The intention is to use web components to encapsulate UI components and their behavior (including self-contained animations) and Julia to read from them and update their attributes. So one can switch to writing web components and using them in Escher if responsiveness is really a concern. With the programming model in Escher, it will be easy to hoist some computations to the browser once there is Julia to JavaScript compilation. However, I don't plan to write the transpiler (yet) ;).
  14. FWIW, I work on Web-related stuff in Julia (like http://shashi.github.io/Escher.jl). I find Julia's type system more natural for general purpose modeling of data than, say, Python's classes. It's also really easy to enforce things like immutability or make stuff blazing fast if one needs to with little effort. Julia's multiple-dispatch is a great companion. On many occasions I've wondered if my code is even complete because it winds up being so small. Another thing to like is the hackability of any code. The standard-library is in Julia, you can look at any function's code from the REPL, and many more developer friendly features.

    Jonathan Malmaud, Iain Dunning, Randy Zwitch, Mike Innes (OP) and many others write and maintain general purpose/web-related library code. I'm sure they will agree with some of what I said.

  15. I love Julia. This is great news! :)

This user hasn’t submitted anything.

Keyboard Shortcuts

Story Lists

j
Next story
k
Previous story
Shift+j
Last story
Shift+k
First story
o Enter
Go to story URL
c
Go to comments
u
Go to author

Navigation

Shift+t
Go to top stories
Shift+n
Go to new stories
Shift+b
Go to best stories
Shift+a
Go to Ask HN
Shift+s
Go to Show HN

Miscellaneous

?
Show this modal