329 karma · joined August 6, 2014
email: hackernews@nprescott.com
Tangential, but does anyone else find this (literal) page odd? It fails to load unless you load in two scripts from cloudfront, where upon it pulls down JQuery, D3, and the following 150+ modules (bundled, of course. I think most of this is for React?):
AutoFocusUtils, BeforeInputEventPlugin, CSSProperty, CSSPropertyOperations, CallbackQueue, ChangeEventPlugin, DOMChildrenOperations, DOMLazyTree, DOMNamespaces, DOMProperty, DOMPropertyOperations, Danger, DefaultEventPluginOrder, EnterLeaveEventPlugin, EventConstants, EventPluginHub, EventPluginRegistry, EventPluginUtils, EventPropagators, FallbackCompositionState, HTMLDOMPropertyConfig, LinkedStateMixin, LinkedValueUtils, PooledClass, React, ReactBrowserEventEmitter, ReactCSSTransitionGroup, ReactCSSTransitionGroupChild, ReactChildReconciler, ReactChildren, ReactClass, ReactComponent, ReactComponentBrowserEnvironment, ReactComponentEnvironment, ReactComponentWithPureRenderMixin, ReactCompositeComponent, ReactCurrentOwner, ReactDOM, ReactDOMButton, ReactDOMComponent, ReactDOMComponentFlags, ReactDOMComponentTree, ReactDOMContainerInfo, ReactDOMDebugTool, ReactDOMEmptyComponent, ReactDOMFactories, ReactDOMFeatureFlags, ReactDOMIDOperations, ReactDOMInput, ReactDOMInstrumentation, ReactDOMOption, ReactDOMSelect, ReactDOMSelection, ReactDOMServer, ReactDOMTextComponent, ReactDOMTextarea, ReactDOMTreeTraversal, ReactDOMUnknownPropertyDevtool, ReactDebugTool, ReactDefaultBatchingStrategy, ReactDefaultInjection, ReactDefaultPerf, ReactDefaultPerfAnalysis, ReactElement, ReactElementValidator, ReactEmptyComponent, ReactErrorUtils, ReactEventEmitterMixin, ReactEventListener, ReactFeatureFlags, ReactFragment, ReactInjection, ReactInputSelection, ReactInstanceMap, ReactInstrumentation, ReactInvalidSetStateWarningDevTool, ReactLink, ReactMarkupChecksum, ReactMount, ReactMultiChild, ReactMultiChildUpdateTypes, ReactNativeComponent, ReactNodeTypes, ReactNoopUpdateQueue, ReactOwner, ReactPerf, ReactPropTypeLocationNames, ReactPropTypeLocations, ReactPropTypes, ReactReconcileTransaction, ReactReconciler, ReactRef, ReactServerBatchingStrategy, ReactServerRendering, ReactServerRenderingTransaction, ReactStateSetters, ReactTestUtils, ReactTransitionChildMapping, ReactTransitionEvents, ReactTransitionGroup, ReactUpdateQueue, ReactUpdates, ReactVersion, ReactWithAddons, ReactWithAddonsUMDEntry, SVGDOMPropertyConfig, SelectEventPlugin, SimpleEventPlugin, SyntheticAnimationEvent, SyntheticClipboardEvent, SyntheticCompositionEvent, SyntheticDragEvent, SyntheticEvent, SyntheticFocusEvent, SyntheticInputEvent, SyntheticKeyboardEvent, SyntheticMouseEvent, SyntheticTouchEvent, SyntheticTransitionEvent, SyntheticUIEvent, SyntheticWheelEvent, Transaction, ViewportMetrics, accumulateInto, adler32, canDefineProperty, createMicrosoftUnsafeLocalFunction, dangerousStyleValue, escapeTextContentForBrowser, findDOMNode, flattenChildren, forEachAccumulated, getEventCharCode, getEventKey, getEventModifierState, getEventTarget, getIteratorFn, getNativeComponentFromComposite, getNodeForCharacterOffset, getTextContentAccessor, getVendorPrefixedEventName, instantiateReactComponent, isEventSupported, isTextInputElement, onlyChild, quoteAttributeValueForBrowser, renderSubtreeIntoContainer, setInnerHTML, setTextContent, shallowCompare, shouldUpdateReactComponent, traverseAllChildren, update, validateDOMNesting, shallowCompare, shallowEqual, invariantFor anyone not seeing the issue: https://i.imgur.com/nT1YoBp.gif
The hot-loading of code is a very nice feature to develop with, but I'm curious to see it in action. Sometimes it feels like Clojurescript's Figwheel won't be topped in this regard (certainly the case with some of the React/webpack tooling).
Nice to see some advancement in Julia, oftentimes I don't hear anything being made with the language and only hear of development in the language itself. I don't see any compelling reason to switch yet but perhaps this will drive cross-pollination in other, similar projects (Jupyter for instance).
It seems there is no styling done to the select element drop-down, which makes for a markedly different look between FF/Safari/Chrome - was this intentional?
Might not be your framework, but I'm experiencing some scroll-jank on the full-height hero image in Chrome (Version 50.0.2661.102 (64-bit)). Doesn't happen in Firefox.
You advertise the size of the framework, (~4kb) but then you include two web fonts which together are more than 10x the size of your framework. It feels a bit misleading only because you lead with the framework size.
Nice job getting it out there.
Gif example: https://i.imgur.com/C2zH4CZ.gif
“It’s like perl without the nastiest bits.”
I think that really does capture the spirit of what this language looks like. I'm not sure it will reach any kind of general applicability, but it seems like a tasteful nod to the extensible nature of Tcl either way. Curious to see the inclusion of PCRE over Tcl's ARE which I thought was pretty routinely trotted out as a better performing, more limited, RE engine. No Newsgroup posts or other media distribution please!For what it's worth, I just opened ST for comparison and it looks nearly identical, fonts render the same between them. I believe ST and Atom have some UI elements that aren't integrated into Emacs out-of-the-box like tabs and mini-maps; is this what you are referring to?