Live data from Hacker News

Julia 1.10

docs.julialang.org

101–104 of 104 posts

Re: Julia 1.10

#101

are my main concerns resolved: • Hello World 200 MB ? • discoverability of functions: object.fun => fun(object) in REPL / IDE? object. => List of applicable functions?

> discoverability of functions I think for the most part this is solved. It works very well and has good integration with VS Code: julia> integrator. EEst accept_step alg cache callback_cache differential_vars do_error_check dt dtacc ... etc. cut short. julia> ODEProblem( ODEProblem(f::SciMLBase.AbstractODEFunction, u0, tspan, args...; kwargs...) @ SciMLBase C:\Users\accou\.julia\dev\SciMLBase\src\problems\ode_proble…

not solved:

julia> x="hi" "hi"

julia> x.

nothing!

Re: Julia 1.10

#102

Earlier quoted context omitted.

> discoverability of functions I think for the most part this is solved. It works very well and has good integration with VS Code: julia> integrator. EEst accept_step alg cache callback_cache differential_vars do_error_check dt dtacc ... etc. cut short. julia> ODEProblem( ODEProblem(f::SciMLBase.AbstractODEFunction, u0, tspan, args...; kwargs...) @ SciMLBase C:\Users\accou\.julia\dev\SciMLBase\src\problems\ode_proble…

not solved: julia> x="hi" "hi" julia> x. nothing!

   julia> propertynames(x)
   ()
Nothing is the correct answer there because there are no properties. `x.y` for any y is an error, so that is correct.

If what you're trying to do is instead discover functions which are compatible with a given signature, you can use what is described in the other post:

    julia> ?("hello", 1, 2.0)[TAB]
    broadcast(f, x::Number...) @ Base.Broadcast broadcast.jl:844
    readuntil(filename::AbstractString, args...; kw...) @ Base io.jl:520
    ...
  
which shows all of the dispatches that match an argument set and thus the functions that can be called on it. Generally the IDE completions do a bit nicer display of that then the REPL though.

Re: Julia 1.10

#103

Earlier quoted context omitted.

Mojo is vapourware from a private company (and we all know how those turn out re programming languages) until proven otherwise.

I'm not sure that's a fair description at this point. They have distributed some SDKs at this point. I really do wish it were open source already though. I know they have laid out a roadmap for opening the source.

The person in charge of Mojo was previously in charge of a massive effort to give tensorflow a new backend, for which he conveniently picked Swift (a language he was also involved in), despite there being better options, only to abandon it halfway through because it was intractable and Swift wasn’t ready/willing to support the compiler changes needed, so he just abandoned it, and now works on Mojo.

It gives real “Jony Ive leaving Apple to go work somewhere where nobody can tell him ‘no’ “ vibes.

Re: Julia 1.10

#104

Earlier quoted context omitted.

I'm not sure that's a fair description at this point. They have distributed some SDKs at this point. I really do wish it were open source already though. I know they have laid out a roadmap for opening the source.

The person in charge of Mojo was previously in charge of a massive effort to give tensorflow a new backend, for which he conveniently picked Swift (a language he was also involved in), despite there being better options, only to abandon it halfway through because it was intractable and Swift wasn’t ready/willing to support the compiler changes needed, so he just abandoned it, and now works on Mojo. It gives real “Jon…

You don't consider developing llvm as an accomplisment?
Post reply on HN