HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
denizyuret
Knet.jl
Jupyter Notebook2016–2020
denizyuret / Knet.jl

Knet.jl

Koç University deep learning framework.

6Distinct people
7Mentions
0Explicit recommenders
1.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Koç University deep learning framework.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year7 dated mentions

Observed mentions: 2016-09-20 18:49:40 UTC to 2020-08-07 19:25:46 UTC.

01232016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC110
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC312
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC202
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101

What Hacker News says

7 sources
I feel I should point out that if you need performance and you're mostly only interested in classic PyTorch or TensorFlow style machine learning (i.e. you don't need Flux.jl's characteristic flexibility), then you should really check out KNet.jl [1]. KNet is generally around the same flexibility and performance as something like PyTorch. It doesn't get nearly as much attention as Flux because it's less novel, but it really should be looked at more. [1] https://github.com/denizyuret/Knet.jl
In JuliaCon2020: Julia Is Production Ready
Yes, there are already a couple. The most well known is a 100% Julia neural network library called Flux.jl [1], which aims to become what Swift for Tensorflow wants as well (to make the entire Julia language a fully differentiable language) through Zygote.jl [2], and even without it has already great integration with the ecosystem, for example with the differentiable equations library through DiffEqFlux.jl [3]. Plus the source code is very high level (while being high performance, including easy GPU support), so you can easily see what each component does and implement any extension directly on your code without worrying about performance. There is also another feature complete native library that allows some very concise code, Knet.jl [4], and the Tensorflow bindings [5]. [1] https://github.com/FluxML/Flux.jl [2] https://github.com/FluxM
Read the rest
In Matlab–Python–Julia Cheatsheet
This is totally fair. Even the Julia creators regularly mention "stay with existing tools for now, if you are happy." Julia is an increasingly attractive option for greenfield, high-performance development, but for folks who aren't doing a lot of that, a more stable language and mature ecosystem is obviously important. Julia and many libraries can still require some elbow-grease, and the maturity and coverage varies between fields. However, this is rapidly changing as folks do new research in Julia and build up everything else they need along the way. The current situation is very similar to SciPy in the mid-2000s, though with perhaps a somewhat different mix of backgrounds. Here are a few examples: https://github.com/JuliaOpt https://github.com/jeff-regier/Celeste.jl https://github.com/dlfivefifty https://github.com/JuliaInv http://docs.
Read the rest
juliadiffeq.org/latest/ https://github.com/denizyuret/Knet.jl http://nemocas.org/ https://juliaplots.github.io/ So, hopefully you'll have reason to take another look in a few years. The most important thing, to me, is that all of these communities want more open, reproducible, and accessible science. There is plenty of room for growth, because users of closed-source software still probably outnumber py/r/jl by 5:1 or more.
In Julia Computing Raises $4.6M in Seed Funding

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.