Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Julia as a CLI Calculator

krasjet.com

Post reply on HN
Print view View original

101–110 of 134 posts

Re: Julia as a CLI Calculator

#102

Post by gen220 »

jaquers wrote: post #68

The typography in this post is beautiful (as well as the content), anybody know where this comes from? Did the author do it by hand or is it something off the shelf? Asking for a friend...

I have a tangential question related to styling (and I agree the styling for this site is wonderful).

When designing your personal/corporate website/blog, how much weight do you attribute to users whose browsers refuse to load remote fonts (by preference or otherwise)?

I ask because I've noticed recently that some websites (notably, many google sites) are unusable, because they depend on remotely-loaded icons, which are replaced with unreadably-stretched alt-text with unintended form factors.

On this blog, for example, the default preformatted-font didn't seem to be monospaced, and the result is that the "julia" name is rendered incorrectly.

All this is meant to ask, do you ever test your designs with browser-default fonts? If not/so, is this conscious? Why?

To be clear, I intend for this to be a survey, not an inquisition. I'm trying to understand this trend better.

For my own answer. At my place of work, in spite of an avowed obsession with accessibility, our designs are regularly sabotaged by browser-default fonts and poorly-rendered alt-text.

Re: Julia as a CLI Calculator

#103

Post by RivieraKid »

dnautics wrote: post #83
RivieraKid wrote: post #26

I really wish there was a language based on Swift that would include most of the nice language, REPL and library characteristics of Julia (and perhaps few from Dart). That would get really close to a "perfect language" for me. Overall I like Julia - and use it as a CLI calculator as well - but there are several things that prevent it from being a good general purpose language: - OOP support is "meh". - str.parse(Int)…

crop(resize(first(images), 100, 100), 25, 25, 75, 75) this will likely get better when julia implements proper pipes, IIRC coming soon in the plans (like elixir does): images |> first |> resize(100,100) |> crop(25, 25, 75, 75) If the language bothers to implement an inspect method (again, like elixir) this is vastly superior to . chaining because you can do this: images |> inspect |> first |> inspect |> resize(100,10…

> This is impossible in oo languages

It's possible in languages which support extensions, such as Swift, Dart or Kotlin.

Re: Julia as a CLI Calculator

#105

Post by newen »

socialdemocrat wrote: post #85
RivieraKid wrote: post #57

Earlier quoted context omitted.

No it's not. OOP is regularly used for new projects by experienced programmers. Julia doesn't have interfaces for example. I know that I can set indexing to be 0-based. Not a good solution.

Most dynamic OOP languages don't have interfaces either, so that is kind of a poor argument. You cannot compare Julia to something like Java. You got to compare it to Ruby, Python etc. Also I have no idea what an interface definition would look like in Julia. A function in Julia isn't bound to one specific type like in an OOP language.

I think interfaces in Julia might go something like

    interface AnimalActions
        function walk(x::Animal) end
        function call(x::Animal, y::Animal) end
        function eat(x::Animal, z::Food) end
    end
    
    struct Dog
and then I guess using it like

    using AnimalActions
    d = Dog("rufus")
    walk(d)

Re: Julia as a CLI Calculator

#106

Post by mcabbott »

dnautics wrote: post #83
RivieraKid wrote: post #26

I really wish there was a language based on Swift that would include most of the nice language, REPL and library characteristics of Julia (and perhaps few from Dart). That would get really close to a "perfect language" for me. Overall I like Julia - and use it as a CLI calculator as well - but there are several things that prevent it from being a good general purpose language: - OOP support is "meh". - str.parse(Int)…

crop(resize(first(images), 100, 100), 25, 25, 75, 75) this will likely get better when julia implements proper pipes, IIRC coming soon in the plans (like elixir does): images |> first |> resize(100,100) |> crop(25, 25, 75, 75) If the language bothers to implement an inspect method (again, like elixir) this is vastly superior to . chaining because you can do this: images |> inspect |> first |> inspect |> resize(100,10…

You can do this:

    @_ images |> filter(size(_,1)>100, __) .|>
    resize(__, 100,100) .|>
    crop(__, 25,25,75,75)
with Underscores.jl. Not exactly `images.first.resize(100, 100).crop(25, 25, 75, 75)` anymore, to point out that this doesn't need every function to prioritise one argument, the pipe feeds into __ in any position. And that .|> applies them to each element.

Re: Julia as a CLI Calculator

#107

Post by krjt »

gen220 wrote: post #102
jaquers wrote: post #68

The typography in this post is beautiful (as well as the content), anybody know where this comes from? Did the author do it by hand or is it something off the shelf? Asking for a friend...

I have a tangential question related to styling (and I agree the styling for this site is wonderful). When designing your personal/corporate website/blog, how much weight do you attribute to users whose browsers refuse to load remote fonts (by preference or otherwise)? I ask because I've noticed recently that some websites (notably, many google sites) are unusable, because they depend on remotely-loaded icons, which…

It's just a small mistake in the CSS file :) Since Julia requires a ton of Unicode characters, I'm using a different monospace type from usual, so I forgot to put the fall back `monospace` at the end of `font-family`, but it's fixed now.

Re: Julia as a CLI Calculator

#108

Post by nsajko »

the_svd_doctor wrote: post #91
nsajko wrote: post #10

A problem with Julia is that it does not parse input numbers with arbitrary precision by default. Example: julia> sin(1.461920290375737576933544899379e+31) -0.9468766486679395 julia> sin(parse(BigFloat, "1.461920290375737576933544899379e+31")) 0.6864670207863400975666631018263839509022548965872940746039593018855528710432756 Fricas is better in this regard, some links: https://en.wikipedia.org/wiki/FriCAS https://fric…

For a "computational math" (ish) language, having FP64 as the default number format seems pretty reasonnable to me. Cases where one needs bignums of course exist, but I think they are less common. Usually if you need arbitrary precision, you know it.

Turns out I wish I could delete my top-level comment now, because I realized that because of Julia's type conversion and promotion semantics a user would actually not get into the problems I worried about.

Re: Julia as a CLI Calculator

#109

Post by wbhart »

29athrowaway wrote: post #104

My personal choice for this is Jupyter and Sagemath.

SageMath takes 3s to load for me (sometimes a lot more if my systems administrator has updated it recently, which seems to happen a lot).

I therefore use Pari/GP for my personal choice. I like the symbolic nature of Pari/GP over Sage or Julia, even though I spend nearly all of my life programming in Julia, and love the language a lot.

However, for computations of trivial things that I want to run really fast, I put them in a function in Julia (so that they are jit-compiled), since nothing will come close to that, by some orders of magnitude.

Re: Julia as a CLI Calculator

#110

Post by dnautics »

BubRoss wrote: post #87
cbkeller wrote: post #66

Earlier quoted context omitted.

Yeah, Julia has had some form of precompilation/caching for ages now, but sorting out all invalidations appears to be highly nontrivial [1] and devs have had more fundamental priorities pre-1.0. There have been some substantial improvements to latency in the meanwhile nonetheless, and PackageCompiler.jl is a viable option as well. [1] https://github.com/JuliaLang/www.julialang.org/pull/794

Just saying caching is difficult doesn't gel with my experience of what seems like low hanging fruit. I realize a lot of Julia ends up being templates, but when just one line of importing the same plotting package always takes 30 seconds or so, I get suspicious of the idea that all the usability warts are super difficult to solve. This has always been a huge complaint for Julia and it seems like one of those things t…

> when things like C++ succeed by not having huge blindsides and pitfalls

what??

Post reply on HN